https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.43.1 2020-03-04T07:29:32+00:00 2020-03-04T07:29:32+00:00 bors bors@rust-lang.org 2020-03-04T07:29:32+00:00 urn:sha1:7a3700c37132385e8e965c18e73d0a09f9146335 Stabilize assoc_int_consts associated int/float constants The next step in RFC https://github.com/rust-lang/rfcs/pull/2700 (tracking issue #68490). Stabilizing the associated constants that were added in #68325. * Stabilize all constants under the `assoc_int_consts` feature flag. * Update documentation on old constants to say they are soft-deprecated and the new ones should be preferred. * Update documentation examples to use new constants. * Remove `uint_macro` and use `int_macro` for all integer types since the macros were identical anyway. r? @LukasKalbertodt 2020-02-26T14:34:30+00:00 Dylan DPC dylan.dpc@gmail.com 2020-02-26T14:34:30+00:00 urn:sha1:e028f26e1df27c257e5007390d1787a256b6eee7 Miscellaneous cleanup to formatting Each commit stands alone. This pull request will also resolve #58320. 2020-02-22T13:12:59+00:00 Dylan DPC dylan.dpc@gmail.com 2020-02-22T13:12:59+00:00 urn:sha1:c261ff1a77f8d5d51d51efd028f937b20146adff Make `u8::is_ascii` a stable `const fn` `char::is_ascii` was already stabilized as `const fn` in #55278, so there is no reason for `u8::is_ascii` to go through an unstable period. cc @rust-lang/libs 2020-02-20T09:49:12+00:00 Dylan DPC dylan.dpc@gmail.com 2020-02-20T09:49:12+00:00 urn:sha1:d96951f5543869567e30ab1c63c0ac44d0d74c30 Make integer exponentiation methods unstably const cc #53718 This makes the following inherent methods on integer primitives into unstable `const fn`: - `pow` - `checked_pow` - `wrapping_pow` - `overflowing_pow` - `saturating_pow` - `next_power_of_two` - `checked_next_power_of_two` - `wrapping_next_power_of_two` Only two changes were made to the implementation of these methods. First, I had to switch from the `?` operator, which is not yet implemented in a const context, to a `try_opt` macro. Second, `next_power_of_two` was using `ops::Add::add` (see the first commit) to "get overflow checks", so I switched to `#[rustc_inherit_overflow_checks]`. I'm not quite sure why the attribute wasn't used in the first place. 2020-02-17T14:18:33+00:00 Mark Rousskov mark.simulacrum@gmail.com 2020-02-15T23:18:13+00:00 urn:sha1:6c45e4540be20b7027ee6364eefc444b432b82ba 2020-02-16T17:53:02+00:00 LeSeulArtichaut leseulartichaut@gmail.com 2020-02-16T17:53:02+00:00 urn:sha1:2ae493a767536b0a5180c788d9ecf2b7ea8bf749 2020-02-15T23:17:51+00:00 Mark Rousskov mark.simulacrum@gmail.com 2020-02-15T23:06:39+00:00 urn:sha1:bd12cd3d2fe2fd69cff05d4b710c8020dea2cdf7 The contents were always UTF-8 anyway, and &str has an equivalent representation to &[u8], so this should not affect performance while removing unsafety at edges. It may be worth exploring a further adjustment that stores a single byte (instead of 16) as the contents are always "", "-", or "+". 2020-02-12T19:20:56+00:00 Linus Färnstrand faern@faern.net 2020-02-08T11:15:22+00:00 urn:sha1:b2dc6187699d99436f6183218d928be09d439578 2020-02-12T19:20:56+00:00 Linus Färnstrand faern@faern.net 2020-02-04T22:08:59+00:00 urn:sha1:83191c2da6da6c13466f7f30568cdea02c761ca0 2020-02-12T19:20:56+00:00 Linus Färnstrand faern@faern.net 2020-02-04T22:00:40+00:00 urn:sha1:086927480be716a14f9c68954d417b544066184b