rust/tests/pretty, branch perf-tmphttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=perf-tmp2025-08-14T18:33:43+00:00Update autodiff tests for the new intrinsics impl2025-08-14T18:33:43+00:00Marcelo Domínguezdmmarcelo27@gmail.com2025-08-14T15:42:14+00:00urn:sha1:cdd4118204e48227fae6a09321b77c7c4a39a186expand: Micro-optimize prelude injection2025-07-28T14:35:09+00:00Vadim Petrochenkovvadim.petrochenkov@gmail.com2025-07-28T14:24:28+00:00urn:sha1:c56f49dc34f43568122f057d72f3472b3fcd4d8e
Use `splice` to avoid shifting the other items twice.
Put `extern crate std;` first so it's already resolved when we resolve `::std::prelude::rust_20XX`.
Update uitest stderrs2025-07-23T11:33:23+00:00Jonathan Brouwerjonathantbrouwer@gmail.com2025-07-12T15:34:43+00:00urn:sha1:3303534dc8825258f8a5d3a1b1e4572d55cccd9a
Signed-off-by: Jonathan Brouwer <jonathantbrouwer@gmail.com>
Rewrite empty attribute lint2025-07-06T07:51:35+00:00Jonathan Brouwerjonathantbrouwer@gmail.com2025-07-04T10:42:33+00:00urn:sha1:3fa0ec91d8f3f14f9514d45d93e6fb7fdf1ad89e
Signed-off-by: Jonathan Brouwer <jonathantbrouwer@gmail.com>
Move the place in `&pin mut $place` when `!Unpin` to ensure soundness2025-06-15T02:31:11+00:00Frank Kingfrankking1729@gmail.com2025-04-04T04:15:23+00:00urn:sha1:afdb54a673243c83660417b540af888f7690f0fbImplement pinned borrows, part of `pin_ergonomics`2025-06-15T02:21:29+00:00Frank Kingfrankking1729@gmail.com2025-01-19T14:01:11+00:00urn:sha1:e627f88f88de85cc52ff1c99a076909084806c98Rollup merge of #134847 - dtolnay:asymmetrical, r=fmease2025-06-13T03:16:54+00:00Matthias Krüger476013+matthiaskrgr@users.noreply.github.com2025-06-13T03:16:54+00:00urn:sha1:b12bb2530b12fedd93a2a54b806a4f8dc2e199c4
Implement asymmetrical precedence for closures and jumps
I have been through a series of asymmetrical precedence designs in Syn, and finally have one that I like and is worth backporting into rustc. It is based on just 2 bits of state: `next_operator_can_begin_expr` and `next_operator_can_continue_expr`.
Asymmetrical precedence is the thing that enables `(return 1) + 1` to require parentheses while `1 + return 1` does not, despite `+` always having stronger precedence than `return` [according to the Rust Reference](https://doc.rust-lang.org/1.83.0/reference/expressions.html#expression-precedence). This is facilitated by `next_operator_can_continue_expr`.
Relatedly, it is the thing that enables `(return) - 1` to require parentheses while `return + 1` does not, despite `+` and `-` having exactly the same precedence. This is facilitated by `next_operator_can_begin_expr`.
**Example:**
```rust
macro_rules! repro {
($e:expr) => {
$e - $e;
$e + $e;
};
}
fn main() {
repro!{return}
repro!{return 1}
}
```
`-Zunpretty=expanded` **Before:**
```console
fn main() {
(return) - (return);
(return) + (return);
(return 1) - (return 1);
(return 1) + (return 1);
}
```
**After:**
```console
fn main() {
(return) - return;
return + return;
(return 1) - return 1;
(return 1) + return 1;
}
```
Update generic tests2025-05-21T07:24:43+00:00Marcelo Domínguezdmmarcelo27@gmail.com2025-05-20T12:36:12+00:00urn:sha1:8917ff602446372e45abed7ab3a58dc879638b1cUpdate codegen and pretty tests2025-05-21T07:24:42+00:00Marcelo Domínguezdmmarcelo27@gmail.com2025-05-10T00:37:15+00:00urn:sha1:2041de7083c114025646220068d3943be517af4a
UI tests are pending, will depend on error messages change.
feat: add generated parameters to generated function2025-05-11T15:54:57+00:00HaeNoegit@haenoe.party2025-04-19T23:10:50+00:00urn:sha1:e2b7278942642b550d3fe1fdbf08640157df60ef
- update pretty printing tests
- only add generic parameters when function is actually generic (no empty turbofish)