https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.44.0 2020-03-29T14:27:07+00:00 2020-03-29T14:27:07+00:00 Mark Rousskov mark.simulacrum@gmail.com 2020-03-27T23:18:52+00:00 urn:sha1:56147219a552b8383e66f9e3e8f0c92ea332aaf4 This renames and stabilizes unsafe floating point to integer casts, which are intended to be the substitute for the currently unsound `as` behavior, once that changes to safe-but-slower saturating casts. 2020-01-06T04:33:31+00:00 Lzu Tao taolzu@gmail.com 2020-01-06T04:33:31+00:00 urn:sha1:c7dbf5ad540402bb6f8f09d9d7f903316232cea5 2019-12-18T17:16:19+00:00 Mark Rousskov mark.simulacrum@gmail.com 2019-12-18T17:00:59+00:00 urn:sha1:82184440ecd33e87cd03a8f7c70af2ad95d5400f 2019-12-08T23:49:30+00:00 Peter peter.wilkins@polecat.com 2019-12-08T23:16:18+00:00 urn:sha1:8f6a06285efe12d778ff7f44067aebeed7b14428 2019-12-06T13:00:45+00:00 Simon Sapin simon.sapin@exyr.org 2019-12-02T08:44:48+00:00 urn:sha1:a213ff82998ef91fa793883c2f2ebbc574967500 This makes `libcore/num/mod.rs` slightly smaller. It’s still 4911 lines and not easy to navigate. This doesn’t change any public API. 2019-12-06T13:01:05+00:00 Simon Sapin simon.sapin@exyr.org 2019-11-28T14:24:26+00:00 urn:sha1:cba479f75c7513f91f727741882a99442f393c12 As discussed in https://github.com/rust-lang/rust/issues/10184 Currently, casting a floating point number to an integer with `as` is Undefined Behavior if the value is out of range. `-Z saturating-float-casts` fixes this soundness hole by making `as` “saturate” to the maximum or minimum value of the integer type (or zero for `NaN`), but has measurable negative performance impact in some benchmarks. There is some consensus in that thread for enabling saturation by default anyway, but provide an `unsafe fn` alternative for users who know through some other mean that their values are in range.