rust - https://github.com/rust-lang/rust

Age	Commit message (Collapse)	Author	Lines
2025-02-10	Show diff suggestion format on verbose replacement	Esteban Küber	-6/+9
	``` error[E0610]: `{integer}` is a primitive type and therefore doesn't have fields --> $DIR/attempted-access-non-fatal.rs:7:15 \| LL \| let _ = 2.l; \| ^ \| help: if intended to be a floating point literal, consider adding a `0` after the period and a `f64` suffix \| LL - let _ = 2.l; LL + let _ = 2.0f64; \| ```
2024-07-12	Make parse error suggestions verbose and fix spans	Esteban Küber	-1/+6
	Go over all structured parser suggestions and make them verbose style. When suggesting to add or remove delimiters, turn them into multiple suggestion parts.
2024-05-02	Stabilize exclusive_range	Ross Smyth	-15/+4

2024-02-04	Suggest `[tail @ ..]` on `[..tail]` and `[...tail]` where `tail` is unresolved	León Orell Valerian Liehr	-5/+56

2024-01-13	Bless tests	George-lewis	-0/+1
	Update tests
2023-11-17	On resolve error of `[rest..]`, suggest `[rest @ ..]`	Esteban Küber	-0/+30
	When writing a pattern to collect multiple entries of a slice in a single binding, it is easy to misremember or typo the appropriate syntax to do so, instead writing the experimental `X..` pattern syntax. When we encounter a resolve error because `X` isn't available, we suggest `X @ ..` as an alternative. ``` error[E0425]: cannot find value `rest` in this scope --> $DIR/range-pattern-meant-to-be-slice-rest-pattern.rs:3:13 \| LL \| [1, rest..] => println!("{rest:?}"), \| ^^^^ not found in this scope \| help: if you meant to collect the rest of the slice in `rest`, use the at operator \| LL \| [1, rest @ ..] => println!("{rest:?}"), \| + ``` Fix #88404.