-
Notifications
You must be signed in to change notification settings - Fork 12.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tracking issue for feature extern_in_paths
#55600
Comments
@rfcbot close Per @petrochenkov's notes above I propose that we remove |
Team member @Centril has proposed to close this. The next step is review by the rest of the tagged teams:
No concerns currently listed. Once a majority of reviewers approve (and none object), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up! See this document for info about what commands tagged team members can give me. |
🔔 This is now entering its final comment period, as per the review above. 🔔 |
The final comment period, with a disposition to close, as per the review above, is now complete. |
@petrochenkov Now that FCP is complete, could you either 1) write up mentoring instructions, 2) fix it up yourself? :) |
…petrochenkov Unaccept `extern_in_paths` Based on completed fcp-close in rust-lang#55600, this removes `extern_in_path` (e.g. `extern::foo::bar`) from the language. The changes are primarily reversing rust-lang@32db83b. Closes rust-lang#55600 r? @petrochenkov
…petrochenkov Unaccept `extern_in_paths` Based on completed fcp-close in rust-lang#55600, this removes `extern_in_path` (e.g. `extern::foo::bar`) from the language. The changes are primarily reversing rust-lang@32db83b. Closes rust-lang#55600 r? @petrochenkov
Allows using
extern
in paths to unambiguously refer to items in extern crates -extern::my_crate::foo
.This feature is superseded by absolute paths
::my_crate::foo
on 2018 edition, and has little value on 2015 edition whereextern crate
items are supposed to be used instead.As a result, the feature is supposed to be removed once 2018 edition ships.
The text was updated successfully, but these errors were encountered: