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

Age	Commit message (Collapse)	Author	Lines
2024-12-10	Keep track of parse errors in `mod`s and don't emit resolve errors for paths ↵	Esteban Küber	-1/+1
	involving them When we expand a `mod foo;` and parse `foo.rs`, we now track whether that file had an unrecovered parse error that reached the end of the file. If so, we keep that information around. When resolving a path like `foo::bar`, we do not emit any errors for "`bar` not found in `foo`", as we know that the parse error might have caused `bar` to not be parsed and accounted for. When this happens in an existing project, every path referencing `foo` would be an irrelevant compile error. Instead, we now skip emitting anything until `foo.rs` is fixed. Tellingly enough, we didn't have any test for errors caused by `mod` expansion. Fix #97734.
2024-04-04	Merge commit '9725c4a162502a02c1c67fdca6b797fe09b2b73c' into ↵	Philipp Krones	-1/+1
	clippy-subtree-update
2023-12-01	Merge commit 'f0cdee4a3f094416189261481eae374b76792af1' into clippy-subtree-sync	Philipp Krones	-1/+1

2022-08-31	Merge commit 'f51aade56f93175dde89177a92e3669ebd8e7592' into clippyup	Jason Newcomb	-1/+1

2022-07-18	Merge commit 'fdb84cbfd25908df5683f8f62388f663d9260e39' into clippyup	Philipp Krones	-9/+17

2022-07-06	Fix `#[expect]` and `#[allow]` for `clippy::duplicate_mod`	xFrednet	-2/+20

2022-05-21	Merge 'rust-clippy/master' into clippyup	xFrednet	-0/+102