https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=master 2025-09-29T01:56:42+00:00 2025-09-29T01:56:42+00:00 Stuart Cook Zalathar@users.noreply.github.com 2025-09-29T01:56:42+00:00 urn:sha1:5373eb12683174e3567067edbe03b704dc99a6cb constify Default on Nanoseconds 2025-09-27T19:26:00+00:00 Matthias Krüger 476013+matthiaskrgr@users.noreply.github.com 2025-09-27T19:26:00+00:00 urn:sha1:bd2e18671d4eb0c2cf33965748c270a8ec358557 update issue number for more_float_constants Update issue number from https://github.com/rust-lang/rust/issues/103883 to https://github.com/rust-lang/rust/issues/146939 r? ``@tgross35`` 2025-09-26T22:41:32+00:00 Mark Rousskov mark.simulacrum@gmail.com 2025-09-14T14:30:29+00:00 urn:sha1:4e9716fbc5fb0f85d838ee9350ade2be5c2a6201 2025-09-26T17:35:29+00:00 Joshua Rayton joshua.rayton@gmail.com 2025-09-26T17:17:31+00:00 urn:sha1:2e904c4d078967abff213637a45386e2676c3757 2025-09-25T20:35:49+00:00 bors bors@rust-lang.org 2025-09-25T20:35:49+00:00 urn:sha1:7ac0330c6d684d86d6f86fabe601a3defdc3b234 Rollup of 8 pull requests Successful merges: - rust-lang/rust#116882 (rustdoc: hide `#[repr]` if it isn't part of the public ABI) - rust-lang/rust#135771 ([rustdoc] Add support for associated items in "jump to def" feature) - rust-lang/rust#141032 (avoid violating `slice::from_raw_parts` safety contract in `Vec::extract_if`) - rust-lang/rust#142401 (Add proper name mangling for pattern types) - rust-lang/rust#146293 (feat: non-panicking `Vec::try_remove`) - rust-lang/rust#146859 (BTreeMap: Don't leak allocators when initializing nodes) - rust-lang/rust#146924 (Add doc for `NonZero*` const creation) - rust-lang/rust#146933 (Make `render_example_with_highlighting` return an `impl fmt::Display`) r? `@ghost` `@rustbot` modify labels: rollup 2025-09-25T16:15:10+00:00 Matthias Krüger 476013+matthiaskrgr@users.noreply.github.com 2025-09-25T16:15:10+00:00 urn:sha1:781f71a6fee007c0b9dc93e2aaf5426ab8e24049 Add doc for `NonZero*` const creation I ran into trouble using `NonZero*` values because I didn’t see any clear way to create them at compile time. At first I ended up using `NonZero*::new_unchecked` a lot, until I realized that `Option::unwrap` and `Option::expect` are `const` and can be used in a `const` context. With that, you can create non-zero values at compile time safely, without touching `unsafe`. This wasn’t obvious to me and my peers who’ve been using Rust for a while, so I thought adding a note to the docs would make it easier for others to discover. If this should be worded differently or placed in another location, we can do that. I just want to make this more obvious. 2025-09-25T15:52:24+00:00 Tim 'Piepmatz' Hesse git+github@cptpiepmatz.de 2025-09-25T15:52:24+00:00 urn:sha1:185ae698aabe0f6f7cc5ef7eeed13a556bce5334 2025-09-25T10:31:54+00:00 Stuart Cook Zalathar@users.noreply.github.com 2025-09-25T10:31:54+00:00 urn:sha1:8e62f95376e40f3eb81e5f1b29cb4eb997c36fb5 unstably constify float mul_add methods Tracking issue: rust-lang/rust#146724 r? `@tgross35` 2025-09-24T19:21:31+00:00 Jeremy Smart jeremy3141592@gmail.com 2025-09-18T19:02:49+00:00 urn:sha1:a00f24116e9bcecc8c73f9f7ec0c399964b37a92 Co-authored-by: Ralf Jung <post@ralfj.de> 2025-09-24T18:34:22+00:00 Matthias Krüger 476013+matthiaskrgr@users.noreply.github.com 2025-09-24T18:34:22+00:00 urn:sha1:2320fc3a3828c0cfc4d1471d9fd30becdd045faa Make missed precondition-free float intrinsics safe So, in my defence, these were both separated out from the other intrinsics in the file *and* had a different safety comment in the stable versions, so, I didn't notice them before. But, in my offence, the entire reason I did the previous PR was because I was using them for SIMD intrinsic fallbacks, and `fabs` is needed for those too, so, I don't really have an excuse. Extra follow-up to rust-lang/rust#146683. r? ```@RalfJung``` who reviewed the previous one These don't appear to be used anywhere outside of the standard locations, at least.