Separate prelude imports from star imports #6971
Draft
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.
Description
Fixes #6119 .
Currently, items implicitly imported from the standard library preludes reside in the same namespace as star imports from non-prelude sources. This means that if a star import imports a name that clashes with a name from a prelude, then using that name in the importing module causes an error.
This PR separates the prelude imports into a different namespace, and allows star imports to shadow prelude imports.
Remaining tasks:
Checklist
Breaking*
orNew Feature
labels where relevant.