Typed tree: create a type's augmentation on first use - #20494
Conversation
An entity now starts with no TyconAugmentation and materialises one atomically on the first TypeContents access, so entities that never gain members hold none. The closed flag moves into EntityFlags, where it is readable without forcing an augmentation into existence, and remapping preserves an absent one. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
❗ Release notes requiredYou can open this PR in browser to add release notes: open in github.dev Caution No release notes found for the changed paths (see table below). Please make sure to add an entry with an informative description of the change as well as link to this pull request, issue and language suggestion if applicable. Release notes for this repository are based on Keep A Changelog format. The following format is recommended for this repository: `* . (PR #XXXXX)`
If you believe that release notes are not necessary for this PR, please add NO_RELEASE_NOTES label to the pull request.
|
|
🔍 Tooling Safety Check — Affects-Bootstrap, Affects-Compiler-Output
|
Every
Entityallocated aTyconAugmentationrecord at construction. An imported IL type never writes toit:
NewILTyconsets exactly one field,tcaug_closed <- true, and most imported types are never askedfor their contents at all.