Implementation status update for recent language and library proposals

Hello, Swift community.

Now that implementation work on Swift 6.4 has largely wrapped up, the Language Steering Group would like to give a quick implementation status report on recent language and standard library proposals. This covers all accepted proposals not already marked as implemented at the time of the Swift 6.3 release.

Proposals implemented in Swift 6.4

Proposals currently expected to be implemented in Swift 6.5

Some of these proposals are already fully implemented; others are still being finished. At this time, there are no proposals accepted in the last year that the implementors are not confident will be implemented in Swift 6.5.

Other proposals

There are several outstanding proposals from more than a year ago that have not yet been fully implemented.

  • SE-0474: Yielding accessors
    • About a year has passed since this proposal was accepted. Implementation work stalled for a few months, but has recently resumed. The implementors are hopeful that this feature will be ready for Swift 6.5, and the LSG does not expect to run a new review if that completes soon.
  • SE-0455: SwiftPM @testable build setting
    • Over a year has passed since this proposal was accepted, and implementation work has stalled. Additionally, the Ecosystem Steering Group has been created and now shares responsibility for this proposal. The ESG is looking into restarting work on this proposal, but we may need to run a new review.
  • SE-0448: Regex lookbehind assertions
    • Over a year has passed since this proposal was accepted, and implementation work has stalled. If work resumes on it, the LSG will likely run a new review just to check that there are no new concerns about the feature.
  • SE-0288: Adding `isPower(of:)` to `BinaryInteger`
    • This feature was added to the Preview package a long time ago. The LSG does not intend to use the Preview package for anything else and would like to see this feature merged into the standard library. This work is not yet scheduled, however.
41 Likes

Is it expected that InlineArray doesn't have a mutating subscript?

This isn’t really the right place for bug reports, but also, InlineArray definitely has a mutating subscript. Maybe you can open a new thread in Using Swift about the problem you’re having?

I think there’s a typo in the link for the @testable proposal: https://github.com/swiftlang/swift-revolution/blob/main/proposals/0455-swiftpm-testable-build-setting.md

(Although swift-revolution does have a nice ring to it)

4 Likes

Fixed, thank you.

1 Like

Should "SE-0516: Iterable" be listed under Swift 6.4 to match the pull request?

1 Like

Oh, yes, fixed.