Use canonical memory allocation dependency in 0.3.x - #9
Merged
Conversation
Collaborator
Author
|
Full off-machine CI passed at head |
This was referenced Jul 29, 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
TestingPerformanceproduct, source, behavior, andfrom: "0.2.0"requirementRelated to #8. This PR does not close the issue because a compatible tag remains separately gated and unauthorized.
Composition evidence
0.2.0at commitafe7e86f16981007b841470d5ea79f0026868bc3MemoryAllocationproductswift-memory-allocation-primitives0.2.0from the canonical.gitURL and records nogithub.com/coenttb/*locationVerification
workspace package resolve: passedworkspace package build --fresh: passed on Swift 6.4workspace package dump-package: preservesTestingPerformanceand the0.2.0..<1.0.0requirementworkspace package test --fresh: all 130 tests built and ran; the unchanged wall-clock testfast operation thresholdfails on this machine at about 151 µs against its fixed 100 µs thresholdThe diff contains no source or test changes. Full off-machine CI is dispatched separately before merge.