aboutsummaryrefslogtreecommitdiff
path: root/crates/hir_def/src/nameres
Commit message (Collapse)AuthorAgeFilesLines
...
* Publish diagnostics for macro expansion errorsJonas Schievink2020-11-271-2/+25
|
* Don't store `SyntaxNodePtr` in `CrateDefMap`Jonas Schievink2020-11-261-4/+2
| | | | It is volatile across reparses and makes incrementality worse.
* Test def map invalidation with #[cfg] below changeJonas Schievink2020-11-261-0/+6
|
* Don't stack overflow on circular modulesAleksey Kladov2020-11-044-18/+62
| | | | closes #6453
* Merge #6435bors[bot]2020-11-031-2/+15
|\ | | | | | | | | | | | | | | 6435: Test Fixture ExplicitRoot + ModuleResolutionRelativePathOutsideRoot. r=matklad a=rickvanprim Updates `module_resolution_relative_path_outside_root` test to check valid paths outside of the root, by moving the root to a subpath so that paths outside of it are possible. If this would be more appropriate as a new test, or if the original check for an invalid path should be left, I'm happy to update. Co-authored-by: James Leitch <[email protected]>
| * Feedback.James Leitch2020-11-021-1/+1
| |
| * Test Fixture ExplicitRoot + ModuleResolutionRelativePathOutsideRoot.James Leitch2020-11-021-2/+15
| |
* | Deny unreachable-pubAleksey Kladov2020-11-021-7/+7
| | | | | | | | | | | | | | | | It's very useful when `pub` is equivalent to "this is crate's public API", let's enforce this! Ideally, we should enforce it for local `cargo test`, and only during CI, but that needs https://github.com/rust-lang/cargo/issues/5034.
* | Handle #![cfg] in crate rootJonas Schievink2020-10-262-2/+22
|/
* Diagnose #[cfg]s in bodiesJonas Schievink2020-10-231-33/+1
|
* Emit better #[cfg] diagnosticsJonas Schievink2020-10-222-12/+39
|
* Add a (hint) diagnostic for unconfigured itemsJonas Schievink2020-10-201-0/+13
|
* Account for proc macro helpers when parsing attrJonas Schievink2020-10-052-1/+9
|
* Add more comments about proc macro resolutionJonas Schievink2020-09-281-0/+20
|
* Reduce visibility of non-proc-macrosJonas Schievink2020-09-182-0/+60
| | | | | proc-macro crates only export proc-macros, but currently other items are also considered public (and show up in completion)
* Remove obsolete proc macro collection codeJonas Schievink2020-09-181-19/+0
| | | | The new attribute-based resolution takes care of this
* Use hir_def to resolve proc macrosJonas Schievink2020-09-181-2/+48
|
* Add testJonas Schievink2020-09-181-0/+32
|
* Rename `CustomDerive` to `ProcMacro`Jonas Schievink2020-09-181-1/+1
| | | | | It handles fn-like macros too, and will handle attribute macros in the future
* Invert condition to unindent codeJonas Schievink2020-09-181-158/+157
|
* Give `ExternCrate` a `Name`, not a `ModPath`Jonas Schievink2020-09-171-10/+7
|
* Don't diagnose imports whose base crate is missingJonas Schievink2020-09-172-17/+64
|
* Add annotation-based nameres diagnostic testsJonas Schievink2020-09-163-38/+108
|
* Track import sources and emit diagnosticsJonas Schievink2020-09-162-21/+60
|
* Leave extern crate items unresolved if they areJonas Schievink2020-09-161-1/+5
|
* Add diagnostic types for unresolved crates/importsJonas Schievink2020-09-161-7/+5
|
* Support extern typesJonas Schievink2020-08-241-0/+2
|
* Switch to expect_test from crates.ioAleksey Kladov2020-08-211-1/+1
|
* Rename ra_hir_def -> hir_defAleksey Kladov2020-08-139-0/+4365