rust/src/libcore/num/dec2flt/mod.rs, branch 1.27.2

Removed the incorrect documentation for from_str

2017-09-05T02:16:15+00:00

Use associated constants in core::num::dec2flt

2017-04-14T15:31:33+00:00

Add missing Eq implementations

2016-09-18T12:26:49+00:00

Use `#[prelude_import]` in `libcore`.

2016-08-24T22:12:23+00:00

std: Stabilize APIs for the 1.11.0 release

2016-07-03T17:49:01+00:00

Although the set of APIs being stabilized this release is relatively small, the trains keep going! Listed below are the APIs in the standard library which have either transitioned from unstable to stable or those from unstable to deprecated. Stable * `BTreeMap::{append, split_off}` * `BTreeSet::{append, split_off}` * `Cell::get_mut` * `RefCell::get_mut` * `BinaryHeap::append` * `{f32, f64}::{to_degrees, to_radians}` - libcore stabilizations mirroring past libstd stabilizations * `Iterator::sum` * `Iterator::product` Deprecated * `{f32, f64}::next_after` * `{f32, f64}::integer_decode` * `{f32, f64}::ldexp` * `{f32, f64}::frexp` * `num::One` * `num::Zero` Added APIs (all unstable) * `iter::Sum` * `iter::Product` * `iter::Step` - a few methods were added to accomodate deprecation of One/Zero Removed APIs * `From> for RangeInclusive` - everything about `RangeInclusive` is unstable Closes #27739 Closes #27752 Closes #32526 Closes #33444 Closes #34152 cc #34529 (new tracking issue)

Fix a couple of dead links on core::num::ParseFloatError docs

2016-04-01T22:46:58+00:00

try! -> ?

2016-03-23T03:01:37+00:00

Automated conversion using the untry tool [1] and the following command: ``` $ find -name '*.rs' -type f | xargs untry ``` at the root of the Rust repo. [1]: https://github.com/japaric/untry

Some docs for std::num

2016-02-09T19:07:51+00:00

This commit does two things: * Re-works the module-level documentation. * Cleaning up wording and adding links to where error types are used. Part of #29364

Prevent the immediate panic uncovered by #31109 and add a test.

2016-02-04T15:28:06+00:00

The code there still triggers an ICE, but for different reasons (const eval unwraps the parse result).

Don't import ParseResult's variants in dec2flt.

2015-12-17T12:48:44+00:00