Fix runtime panic for tagged pointers #19
Merged
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.
This fix adds support for tagged pointers, an internal optimization used by the Objective-C runtime for small objects like short
NSStringsandNSNumbers. These “pointers” may not be aligned, as they encode data directly within the pointer value itself.To support tagged pointers safely, the code now explicitly disables Zig’s runtime alignment safety checks when casting such values. This avoids runtime panics caused by misaligned pointer dereferencing.
The issue was observed when interacting with an Objective-C API that returned a
NSString, which turned out to be a tagged pointer (and not a real heap pointer). The previous implementation assumed proper alignment and thus crashed during a cast operation safety check.