release 0.2.1 with automatic buffer cleanup - #6
Merged
Merged
Conversation
hellerve
force-pushed
the
agent/stringbuf-delete-ownership
branch
from
July 26, 2026 19:08
37e90d2 to
bfd4028
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
1 participant
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.
What changed
StringBuf.deleteas the type's ownership deleter--log-memory0.2.1Why
StringBuf.deletewas registered but not connected to thedeleteinterface. Carp therefore treated buffers as unmanaged and did not emit scope cleanup. In a self-hosted compiler build this retained more than one million 256-byte buffers during specialization.Validation
carp -x --log-memory test/strbuf.carp— 17/17 passed