# Duration has no Rem implementation?

**URL:** <https://internals.rust-lang.org/t/duration-has-no-rem-implementation/16117>\
**Category:** language design\
**Created:** [February 11, 2022, 9:52pm UTC](https://internals.rust-lang.org/t/duration-has-no-rem-implementation/16117 "2022-02-11T21:52:40Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![simbleau](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/simbleau/32/9053_2.png) [@simbleau](https://internals.rust-lang.org/u/simbleau)\
**Post date:** [February 11, 2022, 11:20pm UTC](https://internals.rust-lang.org/t/duration-has-no-rem-implementation/16117/5 "2022-02-11T23:20:48Z")

</div>

As a standard library construct, everything therein should have a high standard of usefulness, which includes eagerly implementing common traits for high operability. Rem, in my humble opinion, is a basic and common operation. Therefore I see Duration lacking basic operability.

To circumnavigate this oversight, one has to convert each duration to nanos, modulo the operands, and reconstruct a duration from the remaining nanos. This is rather poor ergonomics.

---

_[View the full topic](https://internals.rust-lang.org/t/duration-has-no-rem-implementation/16117)._
