-
Notifications
You must be signed in to change notification settings - Fork 2.5k
[SE-0494] small trivially identical updates #3029
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SE-0494] small trivially identical updates #3029
Conversation
|
One might say, trivial updates 😉 |
e4e000b to
236d5f9
Compare
|
@rjmccall All implementation diffs have landed now in latest |
236d5f9 to
84f8fb9
Compare
|
Okay. We don't want to declare it as implemented in a release until the release actually happens, but the rest of this looks fine. |
| * Review Manager: [John McCall](https://github.com/rjmccall) | ||
| * Status: **Accepted with modifications** | ||
| * Implementation: ([String, Substring](https://github.com/swiftlang/swift/pull/82055)), ([Array, ArraySlice, ContiguousArray](https://github.com/swiftlang/swift/pull/82438)), ([Dictionary, Set](https://github.com/swiftlang/swift/pull/82439)) | ||
| * Status: **Implemented (Swift 6.4)** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should use "Swift Next" to correspond to main.
Co-authored-by: Doug Gregor <dgregor@apple.com>
Some small updates to the 0494 proposal:
The status is now implemented on
main.The implementation links include our changes to
SpanandBuffertypes.Some small formatting fixes. GH markdown is a little more forgiving than canonical CommonMark spec. We can change a little formatting like adding extra line breaks before lists and angle brackets around links to better support both specs.
Also added a few extra line breaks in the sample code utility to make it easier to see the effects of the proposal.
The
UTF8Spantype was listed in both "Detailed Design" and "Future Directions". This is an error. When we made the decision to implementUTF8Spanin this proposal it should have been removed from "Future Directions".