internal: Prepare parser interface for editions#16450
Conversation
|
@rustbot author |
|
I've noticed that (including this PR) there are three |
|
The one in |
|
Actually, the span crate depends on the parser through the syntax crate, so we can remove the base-db edition and have the span crate re-export the parser one. |
|
☔ The latest upstream changes (presumably #16492) made this pull request unmergeable. Please resolve the merge conflicts. |
f0bca43 to
e785280
Compare
f8f06d6 to
83370fe
Compare
|
Rebased and deduplicated the enum. The edition field doesn't do anything yet, but I'll merge this as is as a preparation step. Future work can be built on top as a separate PR |
|
Thanks! |
|
☀️ Test successful - checks-actions |
| // FIXME: this should really be using the edition of the method name's span, in case it | ||
| // comes from a macro | ||
| if db.crate_graph()[krate].edition < Edition::Edition2021 { | ||
| if db.crate_graph()[krate].edition < Edition::CURRENT { |
There was a problem hiding this comment.
Shouldn't this stay as Edition2021?
There was a problem hiding this comment.
Good catch, I misread the comment
minor: Fix `rustc_skip_array_during_method_dispatch` edition check CC #16450
internal: Thread edition through to parsing/tt-to-syntax-tree routines for macros Follow up to rust-lang/rust-analyzer#16450, cc rust-lang/rust-analyzer#16324
|
🙏🏾 |
No description provided.