Repository navigation
Integrate the qualified Swift-JSON 1.1 candidate - #16
Merged
Merged
Conversation
# Conflicts: # Scripts/ci.py
ThorFuchs
marked this pull request as ready for review
October 12, 2026 15:21
This was referenced Oct 12, 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.
Integrate the reviewed Swift-JSON 1.1 candidate into main. Scoped typed reads and native value conveniences share cumulative meters; immutable Version 1 payloads preserve exact JSON; wide objects maintain exact-confirmed private indexes. Declare macOS/iOS 27 and qualify public consumers and true disk persistence on Mac, both simulator families and physical iPhone. The explicit maintainer policy accepts iPad simulator qualification for 1.1 and defers physical iPad execution/measurements without claiming them passed.
This aggregate integrates component PRs #8, #9, #10, #11, #12, #13, #14 and #15. Its initial head is exactly
65d86ed758bb7c23f99d1b9e25a4eecc22b11bfd; no source changes are introduced by creating this integration branch. The component histories, original failed receipts and frozen candidates are retained. Review the full main-to-candidate diff and require all protected Native checks for this integration before merge. The maintainer explicitly authorized review and merge; tagging and release publication remain separate.Validation already executed on Swift 6.4 / language 6 / macOS 27 / Xcode and SDK 27.2:
1627529f4ea30aa4483d2a4b3db985b34870353a1eaa53b2c0b268c04b796b9d, clean extracted release tests and byte-identical reproduction. Final source manifest4a909852048f8fb4387fb2cb11ce9a5f5cd7ba2e9335c191ac506671a28c91f6.Performance retains the unchanged 10% review trigger, historical approximately +11% stream disposition and separate approximately +15.76% integrated stream disposition. Measured wide-object benefits include documented small-workload/spare-capacity costs; logical retention is distinct from RSS. SIMD/parallel batches and E11/E12 remain deferred. Apache-2.0 and upstream notices are retained. No tag, package release or protection change is included.