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

Age	Commit message (Collapse)	Author	Lines
2021-09-15	Move some tests to more reasonable directories	Caio	-21/+0

2020-10-26	resolve: private fields in tuple struct ctor diag	David Wood	-1/+1
	This commit improves the diagnostic emitted when a tuple struct is being constructed which has private fields so that private fields are labelled and the message is improved. Signed-off-by: David Wood <david@davidtw.co>
2020-06-21	Prefer accessible paths in 'use' suggestions	Dan Aloni	-6/+6
	This fixes an issue with the following sample: mod foo { mod inaccessible { pub struct X; } pub mod avail { pub struct X; } } fn main() { X; } Instead of suggesting both `use crate::foo::inaccessible::X;` and `use crate::foo::avail::X;`, it should only suggest the latter. It is done by trimming the list of suggestions from inaccessible paths if accessible paths are present. Visibility is checked with `is_accessible_from` now instead of being hard-coded. - Some tests fixes are trivial, and others require a bit more explaining, here are my comments: src/test/ui/issues/issue-35675.stderr: Only needs to make the enum public to have the suggestion make sense. src/test/ui/issues/issue-42944.stderr: Importing the tuple struct won't help because its constructor is not visible, so the attempted constructor does not work. In that case, it's better not to suggest it. The case where the constructor is public is covered in `issue-26545.rs`.
2019-10-27	Point at local similarly named element and tweak references to variants	Esteban Küber	-2/+4
	Point at the span for the definition of ADTs internal to the current crate. Look at the leading char of the ident to determine whether we're expecting a likely fn or any of a fn, a tuple struct or a tuple variant. Turn fn `add_typo_suggestion` into a `Resolver` method.
2019-03-14	Moved issue tests to subdirs and normalised names.	Alexander Regueiro	-0/+19