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

Age	Commit message (Collapse)	Author	Lines
2020-11-28	Move `src/test/rustdoc` intra-doc link tests into a subdirectory	Joshua Nelson	-17/+0
	They were starting to get unwieldy.
2020-08-23	Update primitive test to match the new behavior	Joshua Nelson	-8/+8

2020-08-09	Give precedence to primitives over modules	Joshua Nelson	-1/+6
	This has less surprising behavior when there is a module with the same name as a primitive in scope.
2020-07-30	intra_doc_resolution_failures -> broken_intra_doc_links	Manish Goregaokar	-1/+1

2020-07-30	Rename to intra_doc_resolution_failures	Manish Goregaokar	-1/+1

2020-07-29	Rename usage of intra_doc_link_resolution_failure	Manish Goregaokar	-1/+1

2020-07-16	Fix invalid lint	Joshua Nelson	-1/+1
	intra_doc_resolution_failure is not a lint.
2020-07-05	Always resolve type@primitive as a primitive, not a module	Joshua Nelson	-0/+12
	Previously, if there were a module in scope with the same name as the primitive, that would take precedence. Coupled with https://github.com/rust-lang/rust/issues/58699, this made it impossible to link to the primitive when that module was in scope. This approach could be extended so that `struct@foo` would no longer resolve to any type, etc. However, it could not be used for glob imports: ```rust pub mod foo { pub struct Bar; } pub enum Bar {} use foo::*; // This is expected to link to `inner::Bar`, but instead it will link to the enum. /// Link to [struct@Bar] pub struct MyDocs; ``` The reason for this is that this change does not affect the resolution algorithm of rustc_resolve at all. The only reason we could special-case primitives is because we have a list of all possible primitives ahead of time.