Skip to content

Separate risk checks for overflow and truncation #387

Closed
#478
Closed
Separate risk checks for overflow and truncation#387
#478
Labels
⬇️ affects: code (implementation)Affects implementation details of the code📁 kind: cleanupMaking the library nicer in some way, without affecting functionality much or at all💪 effort: medium
Milestone
0.5.0

Description

@chiphogg
chiphogg
opened on Feb 26, 2025

Given a conversion from one (unit, rep) to another, we should reason separately about overflow and truncation risks. This will pave the way for new APIs in #122.

Metadata

Metadata

Assignees

No one assigned

    Labels

    ⬇️ affects: code (implementation)Affects implementation details of the code📁 kind: cleanupMaking the library nicer in some way, without affecting functionality much or at all💪 effort: medium

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions