mirror of
https://github.com/rust-lang/rust.git
synced 2025-02-03 18:43:38 +00:00
745bd45ddb
4227: Report invalid, nested, multi-segment crate-paths r=matklad a=djrenren
There was a bug in the previous path-validating code that didn't detect multi-segment paths that started with `crate`.
```rust
// Successfully reported
use foo::{crate};
// BUG: was not being reported
use foo::{crate::bar};
```
This was due to my confusion about path-associativity. That is, the path with no qualifier is the innermost path, not the outermost. I've updated the code with a lot of comments to explain what's going on.
This bug was discovered when I found an erroneous `ok` test which I reported here:
https://github.com/rust-analyzer/rust-analyzer/issues/4226
This test now fails and has been modified, hopefully in the spirit of the original test, to be correct. Sorry about submitting the bug in the first place!
Co-authored-by: John Renner <john@jrenner.net>
|
||
|---|---|---|
| .. | ||
| ra_arena | ||
| ra_assists | ||
| ra_cfg | ||
| ra_db | ||
| ra_flycheck | ||
| ra_fmt | ||
| ra_hir | ||
| ra_hir_def | ||
| ra_hir_expand | ||
| ra_hir_ty | ||
| ra_ide | ||
| ra_ide_db | ||
| ra_mbe | ||
| ra_parser | ||
| ra_proc_macro | ||
| ra_proc_macro_srv | ||
| ra_prof | ||
| ra_project_model | ||
| ra_syntax | ||
| ra_text_edit | ||
| ra_tt | ||
| rust-analyzer | ||
| stdx | ||
| test_utils | ||