Carry forward Open Namespaces goal to 2025H2 #322
Merged
Conversation
This file contains hidden or 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
eholk
commented
Jun 26, 2025
|
|
||
| | Metadata | | | ||
| | :-- | :-- | | ||
| | Point of contact | @epage | |
There was a problem hiding this comment.
I'm fine being the overall point of contact and just delegating updates to the specific team currently owning the work.
eholk
commented
Jun 26, 2025
Comment on lines
+33
to
+36
| ### The "shiny future" we are working towards | ||
|
|
||
| ## Design axioms | ||
|
|
There was a problem hiding this comment.
It'd be good to fill out these two sections.
As a design axiom, I think it'd be good to have something about integrating well with the resolver code, preferably leaving it simpler overall.
lqd
reviewed
Jul 18, 2025
Co-authored-by: Rémy Rakic <[email protected]>
nikomatsakis
approved these changes
Jul 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
We'd like to keep working on Open Namespaces for 2025H2. This copies over the previous goal and makes changes according to our plans for the next six months.
Rendered