Preserve interpolation metadata across type copies#10230
Merged
Conversation
rtfeldman
marked this pull request as ready for review
July 19, 2026 17:14
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Static dispatch constraints for string interpolation kept their part metadata in Check-local side tables, so importing a function with an interpolation lost the metadata needed when defaulting from_interpolation to Str. This moves the interpolation payload into the type store as non-identity constraint metadata, remaps it during instantiation and import copy, and keeps canonical type keys and constraint equivalence based only on semantic constraint identity. Fixes #10204.