Repository navigation
Add explicitly owned native byte buffers - #1580
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
sbillig
force-pushed
the
fevm-pr-native-owned-bytes
branch
from
September 23, 2026 06:27
816e91b to
7337f5c
Compare
sbillig
force-pushed
the
fevm-pr-native-owned-bytes
branch
from
September 24, 2026 04:32
7337f5c to
56f075c
Compare
cburgdorf
approved these changes
Sep 24, 2026
sbillig
force-pushed
the
fevm-pr-native-owned-bytes
branch
from
September 25, 2026 00:12
56f075c to
96cc320
Compare
sbillig
force-pushed
the
fevm-pr-native-owned-bytes
branch
from
September 25, 2026 01:13
96cc320 to
b8f0316
Compare
cburgdorf
added a commit
that referenced
this pull request
Sep 30, 2026
Several user-facing changes merged after 26.3 were missing release notes entries: - Bugfixes: event ABI `anonymous` flag (#1562), string literal escapes (#1563), effect provider identity (#1564), shared calls on non-Copy fields (#1581), recursive raw pointer types (#1609). - Performance: `DynArray::get` for static elements (#1559), constant string ABI encoding (#1560), compile-time caching (#1617, #1619, #1621). - Native backend features: workspaces, native tests and `std::io` (#1565), process arguments and CPU timing (#1566), `ByteBuffer` (#1580).
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.
Native programs need reusable heap storage whose growth can fail without losing existing data. Add
std::native::ByteBuffer, an explicit, non-Copy allocation owner with fallible geometric growth, zero initialization, overlap-safe copying, capacity reuse, and consumingrelease.The buffer keeps its allocation private. Its allocator declarations have compiler-owned memory contracts, and native host calls pass raw addresses using the platform pointer ABI. User-defined allocator declarations remain subject to opaque-call checks.
This follows #1579 and pins the Sonatina enum-layout fix from fe-lang/sonatina#328 on the existing aggregate-construction integration. Buffer data is reclaimed explicitly; automatic destruction and compiler-generated reference-descriptor reclamation remain separate work.