rust/src/libstd/num, branch master

std: Flatten the num directory to reflect the module layout

2016-11-01T17:08:24+00:00

This makes it dissimilar to how core is structured on disk, but more predictable on its own.

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

2016-08-24T22:12:48+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)

Use the correct types in float examples

2016-06-22T22:33:07+00:00

test: don't assume anything about the sign of NAN.

2016-06-05T16:17:42+00:00

Deprecate {f32,f64}::abs_sub.

2016-05-16T22:06:56+00:00

The abs_sub name is misleading: the function actually computes the positive difference (`fdim` in C), not the `(x - y).abs()` that *many* people expect from the name. This function can be replaced with just `(x - y).max(0.0)`, mirroring the `abs` version, but this behaves differently with NAN: `NAN.max(0.0) == 0.0`, while `NAN.positive_diff(0.0) == NAN`. People who absolutely need that behaviour can use the C function directly and/or talk to the libs team (we haven't encountered a concrete use-case for this functionality). Closes #30315.

Implement RFC 1542

2016-05-07T15:52:41+00:00

cc #33417

std: Add compatibility with android-9

2016-04-27T16:28:48+00:00

The Gecko folks currently use Android API level 9 for their builds, so they're requesting that we move back our minimum supported API level from 18 to 9. Turns out, ABI-wise at least, there's not that many changes we need to take care of. The `ftruncate64` API appeared in android-12 and the `log2` and `log2f` APIs appeared in android-18. We can have a simple shim for `ftruncate64` which falls back on `ftruncate` and the `log2` function can be approximated with just `ln(f) / ln(2)`. This should at least get the standard library building on API level 9, although the tests aren't quite happening there just yet. As we seem to be growing a number of Android compatibility shims, they're now centralized in a common `sys::android` module.

Fix f32::sin_cos and f64::sin_cos examples

2016-04-16T06:42:37+00:00

fallout in existing tests

2016-03-25T10:45:42+00:00