You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The crate also has some correctness issues and appears to be unmaintained.
Alternatives
For quickly parsing floating-point numbers third-party crates are no longer needed. A fast float parsing algorith by the author of lexical has been merged into libcore.
For quickly parsing integers, consider atoi and btoi crates (100% safe code). atoi_radix10 provides even faster parsing, but only with -C target-cpu=native, and at the cost of some unsafe.
For formatting integers in a #[no_std] context consider the numtoa crate.
For working with big numbers consider num-bigint and num-traits.
lexical
6.1.1
lexical
contains multiple soundness issues:BytesIter
trait has safety invariants but is public and not markedunsafe
write_float()
callsMaybeUninit::assume_init()
on uninitialized data, which is is not allowed by the Rust abstract machineThe crate also has some correctness issues and appears to be unmaintained.
Alternatives
For quickly parsing floating-point numbers third-party crates are no longer needed. A fast float parsing algorith by the author of
lexical
has been merged into libcore.For quickly parsing integers, consider
atoi
andbtoi
crates (100% safe code).atoi_radix10
provides even faster parsing, but only with-C target-cpu=native
, and at the cost of someunsafe
.For formatting integers in a
#[no_std]
context consider thenumtoa
crate.For working with big numbers consider
num-bigint
andnum-traits
.See advisory page for additional details.
The text was updated successfully, but these errors were encountered: