Skip to content

Conversation

@mu001999
Copy link

Companion PR to rust-lang/rust#146972

@rustbot rustbot added the S-waiting-on-review Status: The marked PR is awaiting review from a maintainer label Jan 16, 2026
@mu001999 mu001999 marked this pull request as draft January 16, 2026 15:04
@rustbot rustbot removed the S-waiting-on-review Status: The marked PR is awaiting review from a maintainer label Jan 16, 2026
@traviscross traviscross added S-waiting-on-stabilization Waiting for a stabilization PR to be merged in the main Rust repository S-waiting-on-review Status: The marked PR is awaiting review from a maintainer I-lang-docs-nominated Nominated for discussion during a lang-docs team meeting. labels Jan 21, 2026
ehuss and others added 8 commits January 25, 2026 09:09
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.
@ehuss
Copy link
Contributor

ehuss commented Jan 25, 2026

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/.

@mu001999
Copy link
Author

It looks like I don't have permission to push to this branch.

@ehuss I have invited you :). Or I can merge your branch directly

@traviscross
Copy link
Contributor

@mu001999: If you could, please check the box that allows maintainers to push to your branch. (See, e.g., here for details.)

@mu001999
Copy link
Author

mu001999 commented Jan 28, 2026

please check the box that allows maintainers to push to your branch

@traviscross Sadly, this seems to be only available for forks in personal accounts (link):

Pull request authors can give these permissions when they initially create a pull request from a fork in a personal account

@ehuss ehuss force-pushed the doc/import-path-kw branch from 6243ecf to ef94e6a Compare January 29, 2026 15:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

I-lang-docs-nominated Nominated for discussion during a lang-docs team meeting. S-waiting-on-review Status: The marked PR is awaiting review from a maintainer S-waiting-on-stabilization Waiting for a stabilization PR to be merged in the main Rust repository

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants