6 Commits

Author	SHA1	Message	Date
Esteban Küber	f0845adb0c	Show diff suggestion format on verbose replacement ... ``` 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; | ```	2025-02-10 20:21:39 +00:00
Esteban Küber	692bc344d5	Make parse error suggestions verbose and fix spans ... 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-07-12 03:02:57 +00:00
Ross Smyth	6967d1c0fc	Stabilize exclusive_range	2024-05-02 19:42:31 -04:00
León Orell Valerian Liehr	285d8c225d	Suggest [tail @ ..] on [..tail] and [...tail] where tail is unresolved	2024-02-04 22:16:21 +01:00
George-lewis	d56cdd48cb	Bless tests ... Update tests	2024-01-13 12:46:58 -05:00
Esteban Küber	5c3e01a340	On resolve error of [rest..], suggest [rest @ ..] ... 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.	2023-11-17 00:55:55 +00:00