uom
uom copied to clipboard
iliekturtles
Units of measurement -- type-safe zero-cost dimensional analysis
See https://internals.rust-lang.org/t/help-us-test-the-breaking-bug-fix-to-cargo-features/7317 and https://github.com/rust-lang/cargo/issues/5364. Also see the current [`.travis.yml`](https://github.com/iliekturtles/uom/blob/e486174dfd7af0bd0b7f695227a8b97f2cbe29ee/.travis.yml#L34) where `cargo test` is run once for `uom` and once for `feature_check`. Currently if you use `cargo --test --all` workspace crates...
- [ ] saturating_add - [ ] saturating_sub - [ ] saturating_mul - [x] num::Saturating
- [ ] wrapping_abs - [ ] wrapping_add - [ ] wrapping_div - [ ] wrapping_mul - [ ] wrapping_neg - [ ] wrapping_rem - [ ] wrapping_shl (?) -...
- [ ] overflowing_abs - [ ] overflowing_add - [ ] overflowing_div - [ ] overflowing_mul - [ ] overflowing_neg - [ ] overflowing_rem - [ ] overflowing_shl (?) -...
It would be excellent to have serde serialize to strings with unit abbreviations so that the types are carried in serialization.
Support external underlying storage types. e.g. `Quantity`. Currently this isn't feasible because units must implement `Conversion`. This implementation is currently generated in the `quantity!` macro for specific types using the...
Handle overflows in conversion factors so that factors that exceed the underlying storage type's min/max values do not cause errors. Currently tests are failing because conversion factors overflow the underlying...
I didn't realize that I didn't have integers enabled when running tests until I tried to write integer-specific tests for the new Saturating support I'm working on. When I tried...
I haven't had a chance to dig into this yet but I noticed a crash when trying to create reasonably large `u64` Lengths. This is some example code that fails...
Metadata
Owner
Metadata
Units of measurement -- type-safe zero-cost dimensional analysis