3 ms·
That's discussed in the article. "The current state isn’t necessarily the final state of overflow checking: the RFC even mentioned some future directions. Rust
by pcwalton 11y ago
That's discussed in the article.
"The current state isn’t necessarily the final state of overflow checking: the RFC even mentioned some future directions. Rust could introduce operators like Swift’s wrapping +% in future, something that was not done initially because Rust tries to be conservative and reasonably minimal, as well as hypothetically having scoped disabling of overflow checking (e.g. a single function could be explicitly marked, and its internals would thus be unchecked in all modes). There’s interest in the latter particularly, from some of Rust’s keenest (potential) users Servo and Gecko."
- zzzcpan 11y agoYes, I know. But more operators is the solution, it removes all that ambiguity with multiple intents and simplifies a lot of things.