Fix string ABI and place traversal duplication - #68
Merged
Conversation
This was referenced Aug 11, 2026
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
@expras one direct raw-address operation through MIR and LLVM place pointers.Validation
CCACHE_DISABLE=1 GOCACHE=/tmp/peeper-go-cache go test -count=1 ./...CCACHE_DISABLE=1 GOCACHE=/tmp/peeper-go-cache go build ./...CCACHE_DISABLE=1 GOCACHE=/tmp/peeper-go-cache go vet ./...gofmtandgit diff --checkTracking
Progresses #29 (Define string runtime semantics). Remaining C/FFI boundary and runtime-construction work stays open under #29.
Stack
This is stack base. Follow-ups are #69 (32-bit ABI/intrinsics), #70 (contract spine), #71 (end-to-end remediation), and #72 (open-ended default range cloning).