Replace unsafe iteration with use of Span#242
Closed
airspeedswift wants to merge 1 commit into
Closed
Conversation
airspeedswift
requested review from
RuiyuZhu,
fboemer and
karulont
as code owners
fboemer
reviewed
Nov 19, 2025
| @@ -1,4 +1,4 @@ | |||
| // swift-tools-version: 6.0 | |||
| // swift-tools-version: 6.2 | |||
Contributor
There was a problem hiding this comment.
Mind updating the README (https://github.com/apple/swift-homomorphic-encryption?tab=readme-ov-file#swift--xcode-versions) as well?
We'll also need to add swift 6.0 & 6.1 to
Member
Author
|
superseded by #258 |
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
2 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.
This replaces a number of
withUnsafeblocks with use of the.spanproperty. This was introduced in Swift 6.2, so it does require bumping the toolchain version and minimum Mac deployment target.Some minor performance regressions should be anticipated, as there will now be bounds checks performed where previously these were compiled out with the use of unsafe buffers. These either should be accepted as the cost of memory safety, or investigated to see if tweaks to the code structure could help the compiler eliminate them.