Make Monotype function identities explicit#9639
Draft
rtfeldman wants to merge 1 commit into
Draft
Conversation
09886fc to
33e7068
Compare
33e7068 to
95019c9
Compare
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
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.
Monotype now assigns explicit function specialization ids during lowering and threads them through function values and direct calls, so lifting can map ids directly instead of reconstructing identity from FnTemplate digests. Deferred top-level specializations reserve their function ids before their bodies are lowered, and nested/lambda specializations reuse the same Monotype-owned ids. This removes the lifter's template-family fallback and makes B101 an active regression test.\n\nFixes #9519.