https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=try-perf 2025-09-11T01:10:46+00:00 2025-09-11T01:10:46+00:00 Jieyou Xu jieyouxu@outlook.com 2025-09-11T01:00:01+00:00 urn:sha1:b38a86f4d7c28ae9ab153b87c7e45037e56306fb This reverts commit 1eeb8e8b151d1da7daa73837a25dc5f7a1a7fa28, reversing changes made to 324bf2b9fd8bf9661e7045c8a93f5ff0ec1a8ca5. Unfortunately the assert desugaring change is not backwards compatible, see RUST-145770. Code such as ```rust #[derive(Debug)] struct F { data: bool } impl std::ops::Not for F { type Output = bool; fn not(self) -> Self::Output { !self.data } } fn main() { let f = F { data: true }; assert!(f); } ``` would be broken by the assert desugaring change. We may need to land the change over an edition boundary, or limit the editions that the desugaring change impacts. 2025-08-19T04:18:22+00:00 Stuart Cook Zalathar@users.noreply.github.com 2025-08-19T04:18:22+00:00 urn:sha1:f3f1847e40f0b33dcf7bee55af49054f7ec1875c rework GAT borrowck limitation error The old one depends on the `ConstraintCategory` of the constraint which meant we did not emit this note if we had to prove the higher ranked trait bound due to e.g. normalization. This made it annoying brittle and caused MIR borrowck errors to be order dependent, fixes the issue in https://github.com/rust-lang/rust/pull/140737#discussion_r2259592651. r? types cc ```@amandasystems``` 2025-08-14T15:43:39+00:00 lcnr rust@lcnr.de 2025-08-13T12:08:53+00:00 urn:sha1:3ebf611005370734ddf7ce22e41ac502e4fff59a 2025-08-13T12:03:26+00:00 lcnr rust@lcnr.de 2025-08-07T09:30:24+00:00 urn:sha1:a95a2ac476ef04ccf8cfabd35e6fcdb9569f053d 2025-08-12T16:30:48+00:00 Esteban Küber esteban@kuber.com.ar 2024-03-17T20:46:36+00:00 urn:sha1:c439a59dbd275aef9bc24c7172e2111ccc3794c3 In the desugaring of `assert!`, we now expand to a `match` expression instead of `if !cond {..}`. The span of incorrect conditions will point only at the expression, and not the whole `assert!` invocation. ``` error[E0308]: mismatched types --> $DIR/issue-14091.rs:2:13 | LL | assert!(1,1); | ^ expected `bool`, found integer ``` We no longer mention the expression needing to implement the `Not` trait. ``` error[E0308]: mismatched types --> $DIR/issue-14091-2.rs:15:13 | LL | assert!(x, x); | ^ expected `bool`, found `BytePos` ``` `assert!(val)` now desugars to: ```rust match val { true => {}, _ => $crate::panic::panic_2021!(), } ``` Fix #122159. We make some minor changes to some diagnostics to avoid span overlap on type mismatch or inverted "expected"/"found" on type errors. We remove some unnecessary parens from core, alloc and miri. address review comments 2025-07-29T14:08:15+00:00 Oli Scherer github333195615777966@oli-obk.de 2025-07-24T10:19:20+00:00 urn:sha1:75bdbf25e39f073b35eadedcf575affac7762a86 2025-07-24T21:01:44+00:00 Oneirical manchot@videotron.ca 2025-07-13T19:56:27+00:00 urn:sha1:a924d44115b632775ef0d2e12382e285953b0c2c 2025-06-09T14:08:12+00:00 Jack Wrenn jack@wrenn.fyi 2025-06-04T15:58:01+00:00 urn:sha1:e9eae28eee0a99c64e81f4fdf87d3c76241e56bd Previously, `rustc_transmute`'s layout representations were genericized over `R`, a reference. Now, it's instead genericized over representations of type and region. This allows us to move reference transmutability logic from `rustc_trait_selection` to `rustc_transmutability` (and thus unit test it independently of the compiler), and — in a follow-up PR — will make it possible to support analyzing function pointer transmutability with minimal surgery. 2025-06-07T11:42:30+00:00 Ralf Jung post@ralfj.de 2025-06-07T09:32:09+00:00 urn:sha1:17946c22b1d7abd2dd990bf6998c8491b534fe62 also adjust the wording a little so that we don't say "the error occurred here" for two different spans 2025-06-04T17:50:24+00:00 Matthias Krüger 476013+matthiaskrgr@users.noreply.github.com 2025-06-04T17:50:24+00:00 urn:sha1:23ba088502f4e05a9f79cfa6e6a3494161d5f09e Ensure query keys are printed with reduced queries Using `-Z query-dep-graph` and debug assertions leads to an ICE that was originally discovered in rust-lang/rust#141700: > This isn't an incremental bug per se, but instead a bug that has to do with debug printing query keys when debug assertions and `-Z query-dep-graph` is enabled. We end up printing a const (b/c we're using generic const args here) whose debug printing for -Z query-dep-graph requires invoking the same query cyclically 😃 > > I've pushed a commit which should fix this. This isn't related to the standard library changes, but instead b/c it seems to be the first usage of `feature(adt_const_params)` in the standard library that ends up being triggered in incremental tests. r? oli-obk