rust/src/libcore/fmt/num.rs, branch 1.27.2

Rollup merge of #49103 - glandium:uninitialized, r=cramertj

2018-03-26T13:14:56+00:00

Use an uninitialized buffer in GenericRadix::fmt_int, like in Display::fmt for numeric types The code using a slice of that buffer is only ever going to use bytes that are subsequently initialized.

Rollup merge of #49102 - glandium:decimal, r=aturon

2018-03-23T17:16:09+00:00

Remove core::fmt::num::Decimal Before ebf9e1aaf6, it was used for Display::fmt, but ebf9e1aaf6 replaced that with a faster implementation, and nothing else uses it.

Rollup merge of #49099 - glandium:master, r=sfackler

2018-03-19T23:15:22+00:00

Use associated consts for GenericRadix base and prefix The trait being private, this does not imply an API change.

Use associated consts for GenericRadix base and prefix

2018-03-17T06:49:37+00:00

Use an uninitialized buffer in GenericRadix::fmt_int, like in Display::fmt for numeric types

2018-03-17T01:42:34+00:00

The code using a slice of that buffer is only ever going to use bytes that are subsequently initialized.

Remove core::fmt::num::Decimal

2018-03-17T01:32:31+00:00

Before ebf9e1aaf6, it was used for Display::fmt, but ebf9e1aaf6 replaced that with a faster implementation, and nothing else uses it.

Add hexadecimal formatting of integers with fmt::Debug

2018-03-13T13:53:06+00:00

This can be used for integers within a larger types which implements Debug (possibly through derive) but not fmt::UpperHex or fmt::LowerHex. ```rust assert!(format!("{:02x?}", b"Foo\0") == "[46, 6f, 6f, 00]"); assert!(format!("{:02X?}", b"Foo\0") == "[46, 6F, 6F, 00]"); ``` RFC: https://github.com/rust-lang/rfcs/pull/2226

Added inline to fmt for debug implementations of primitives.

2018-01-29T04:55:05+00:00

Reject '2' as a binary digit in internals of 'b' formatting

2017-11-29T05:35:18+00:00

I don't believe the previous code `0 ... 2` would run into any real problems, but it seems confusing to read, given that '2' is never a valid binary digit. As far as I can tell this code is only ever called from within another private method in the trait which has logic to never hand it '2' anyways. I thought we could change this for clarity anyways.

address some `FIXME`s whose associated issues were marked as closed

2017-09-30T08:33:47+00:00

remove FIXME(#13101) since `assert_receiver_is_total_eq` stays. remove FIXME(#19649) now that stability markers render. remove FIXME(#13642) now the benchmarks were moved. remove FIXME(#6220) now that floating points can be formatted. remove FIXME(#18248) and write tests for `Rc` and `Rc<[u8]>` remove reference to irelevent issues in FIXME(#1697, #2178...) update FIXME(#5516) to point to getopts issue 7 update FIXME(#7771) to point to RFC 628 update FIXME(#19839) to point to issue 26925