Expand on the guide-level explanation #4
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is pulled from rust-lang#3243 (comment) This shifted the guide to starting from the consumer of a namespace, as that is the majority case, and then moving into the role of a crate owner. This leaves out details on feature flags to not duplicate a future "why not feature flags" section.
Manishearth
reviewed
Mar 27, 2022
| ``` | ||
|
|
||
| In case there is also an in-scope crate `foo` with an exported `bar` item, this will cause an ambiguity error unless both the item `foo::bar` and the crate `foo::bar` are actually resolving to the same item. This is similar to what rustc already does when it encounters in-use clashes in glob imports. | ||
| Some reasons for `foo`s owner to consider using namespaces: | ||
| - Avoid name conflicts with third-party authors (since they are reserved) |
There was a problem hiding this comment.
I wonder if some of this should be duplicated in the motivation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is pulled from rust-lang#3243 (comment)
This shifted the guide to starting from the consumer of a namespace, as
that is the majority case, and then moving into the role of a crate
owner.
This leaves out details on feature flags to not duplicate a future "why
not feature flags" section.