NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
crates.io · #2364 most downloaded on crates.io
Numeric types that cannot hold maximum values
Last release 3 years ago
no release in 18 months
Release timing varies
gaps range from 9 days to 1.7 years
Nearly every release is documented
notes for 8 of 8 stable releases
1 version withdrawn
withdrawn after publishing
6 years old
9 releases · first in 2020
One column per quarter.
Fixed serde feature not working in no_std contexts ([#16])
serde feature not working in no_std contexts (#16)Added ZERO, ONE, and MAX associated constants. ([#15])
ZERO, ONE, and MAX associated constants. (#15)Fixed PartialOrd and Ord implementations being backwards.
PartialOrd and Ord implementations being backwards.(bad release, yanked)
(bad release, yanked)
Implemented Default for NonMax*.
Default for NonMax*.serde when the corresponding feature is enabled.Raised MSRV to 1.47.0 to eliminate unsafe in new.
unsafe in new.NonMaxI128 and NonMaxU128.std::convert::[Try]From for NonMax* and primitive types to match NonZero*.std::fmt::{Display, Binary, Octal, LowerHex, UpperHex} to match NonZero*.impl Debug for NonMax*, to match NonZero*.std::str::FromStr for NonMax* to match NonZero*.std::ops::BitAnd[Assign] for NonMax*, similar to BitOr[Assign] for NonZero*.no_std support.Raised MSRV to 1.46.0 to make more methods const.
const.const.Fix casing for NonMaxIsize and NonMaxUsize. D'oh.
Fix casing for NonMaxIsize and NonMaxUsize. D'oh.
Woops, the first version is 0.2.0 I guess
Woops, the first version is 0.2.0 I guess
Your coding agent can read these notes before it upgrades. Set up the MCP server →