-
Notifications
You must be signed in to change notification settings - Fork 572
Document importing path-segment keyword #2136
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
base: master
Are you sure you want to change the base?
Conversation
As with other parts of the reference, the structure is moving more towards a set of rules, and the bullet list here isn't necessary.
This note was more of a general commentary on `self`, and was not specifically attached to its previous rule of items.use.self.namespace.
This is somewhat duplicated with the `self` section and the restrictions section which already describes about renaming.
This moves `$crate` to be next to `crate` since they are closely related.
This tries to simplify the wording and to maintain consistency, since they are all essentially saying the same thing.
The rules in the paths chapter don't entirely reflect what a valid path in a `use` declaration is. I'm not entirely sure what's the best approach for describing how paths work since there are several differences between `use` paths and expression paths.
|
It looks like I don't have permission to push to this branch. I have pushed my edits to https://github.com/ehuss/reference/commits/doc/import-path-kw/. |
@ehuss I have invited you :). Or I can merge your branch directly |
@traviscross Sadly, this seems to be only available for forks in personal accounts (link):
|
6243ecf to
ef94e6a
Compare
Companion PR to rust-lang/rust#146972