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

Age	Commit message (Collapse)	Author	Lines
2025-04-03	compiletest: Require `//~` annotations even if `error-pattern` is specified	Vadim Petrochenkov	-1/+1

2025-02-21	Trim suggestion part before generating highlights	Michael Goulet	-1/+1

2025-02-21	More sophisticated span trimming	Michael Goulet	-2/+1

2025-02-10	Show diff suggestion format on verbose replacement	Esteban Küber	-1/+2
	``` 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-01-10	Stop mentioning internal lang items in no_std binary errors	Nilstrieb	-3/+3
	When writing a no_std binary, you'll be greeted with nonsensical errors mentioning lang items like eh_personality and start. That's pretty bad because it makes you think that you need to define them somewhere! But oh no, now you're getting the `internal_features` lint telling you that you shouldn't use them! But you need a no_std binary! What now? No problem! Writing a no_std binary is super easy. Just use panic=abort and supply your own platform specific entrypoint symbol (like `main`) and you're good to go. Would be nice if the compiler told you that, right? This makes it so that it does do that.
2023-01-11	Move /src/test to /tests	Albert Larsan	-0/+22