fix: heap-allocate map/set structs to prevent class field segfaults#318
Merged
fix: heap-allocate map/set structs to prevent class field segfaults#318
Conversation
…t class field segfaults
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.
Summary
alloca) for the collection struct. When stored in class fields, the stack frame is freed after the constructor returns, leaving a dangling pointer — causing segfaults on later access.variable-allocator.tsto useGC_malloc(heap allocation), matching the pattern already used by the literal generators inmap.tsandset.ts.Test plan
maps/map-class-field.ts— Map stored in class field, accessed after constructionnpm run verify:quickpasses (tests + self-hosting Stage 1)🤖 Generated with Claude Code