https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=try-perf 2025-09-26T13:33:48+00:00 2025-09-26T13:33:48+00:00 Guillaume Gomez guillaume1.gomez@gmail.com 2025-09-26T11:59:06+00:00 urn:sha1:a535c7be5444fb6584eecc99f53e6cdb710ff70f 2025-09-24T00:47:34+00:00 Caleb Zulawski caleb.zulawski@gmail.com 2025-09-16T06:23:24+00:00 urn:sha1:f5c6c9542ecfab74e654f9b7f1150d486560ae43 Unify zero-length and oversized SIMD errors 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-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-08-07T21:18:00+00:00 Esteban Küber esteban@kuber.com.ar 2025-07-16T19:45:07+00:00 urn:sha1:99196657fcb5c1e20c13e76166c7f52d35584e88 `TyCtxt::short_string` ensures that user visible type paths aren't overwhelming on the terminal output, and properly saves the long name to disk as a side-channel. We already use these throughout the compiler and have been using them as needed when users find cases where the output is verbose. This is a proactive search of some cases to use `short_string`. We add support for shortening the path of "trait path only". Every manual use of `short_string` is a bright marker that that error should be using structured diagnostics instead (as they have proper handling of long types without the maintainer having to think abou tthem). When we don't actually print out a shortened type we don't need the "use `--verbose`" note. On E0599 show type identity to avoid expanding the receiver's generic parameters. Unify wording on `long_ty_path` everywhere. 2025-07-26T06:15:08+00:00 Trevor Gross t.gross35@gmail.com 2025-07-26T06:15:08+00:00 urn:sha1:6b1b68f4ee9314e4286f98d38f8b0f3cde3938c5 Add `ignore-backends` annotations in failing GCC backend ui tests Follow-up of https://github.com/rust-lang/rust/pull/144125. In the GCC backend, we don't support all ui tests yet and we have a list of tests we currently ignore available [here](https://github.com/rust-lang/rustc_codegen_gcc/blob/master/tests/failing-ui-tests.txt). This PR adds the `ignore-backends` annotations to the corresponding ui tests. The second commit is a fix to compiletest, complaining about `ignore-backends`. r? ```@jieyouxu``` 2025-07-24T17:18:37+00:00 Scott McMurray scottmcm@users.noreply.github.com 2025-07-24T05:13:05+00:00 urn:sha1:01524abb05a4a60d0015972811b8bbb9bd2a73d3 This just uses the `valid_range` from the backend, so it's duplicating the range metadata that now we include on parameters and loads. 2025-07-23T11:48:04+00:00 Guillaume Gomez guillaume1.gomez@gmail.com 2025-07-23T11:31:22+00:00 urn:sha1:de93fb13feeb6263bef61d4035e78ab8651c5714 2025-07-20T17:22:09+00:00 Scott McMurray scottmcm@users.noreply.github.com 2025-03-07T03:13:46+00:00 urn:sha1:41ce1ed252f194756fb2f3e3e92bbdfb3940088d 2025-07-20T17:15:14+00:00 Scott McMurray scottmcm@users.noreply.github.com 2025-07-12T09:33:42+00:00 urn:sha1:08b816ff18347031b1160f1257cde2008c3c366e