Repository navigation
Enable strict memory safety - #16
Open
achristensen07 wants to merge 1 commit into
Open
achristensen07 wants to merge 1 commit into
achristensen07 wants to merge 1 commit into
Conversation
achristensen07
requested review from
agnosticdev,
ekinnear,
kpodosin and
tfpauly
as code owners
September 3, 2026 00:22
kpodosin
approved these changes
Sep 3, 2026
baumanl
self-requested a review
September 3, 2026 17:29
baumanl
approved these changes
Sep 3, 2026
achristensen07
force-pushed
the
strict-memory-safety
branch
from
September 4, 2026 15:01
798a43f to
6b2bd53
Compare
achristensen07
force-pushed
the
strict-memory-safety
branch
from
September 4, 2026 17:04
6b2bd53 to
d824a49
Compare
Author
|
We can either wait until support for Swift 6.3 is dropped, or we can add a few dozen extra unsafes that show up as warnings with Swift 6.4+ like this: |
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
3 participants
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.
And add any unsafe keywords needed to fix the build.