You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SR-7140 Implement generators and adopt them in the standard library
SR-7141 Implement proof-of-concept for move-only types to make sure the standard library can support move-only data
SR-7100 Change default ownership for passing parameters to use the "guaranteed" convention
SR-7135 Implement generalized accessors and adopt them in the standard library
SR-7134 Implement coroutines so that they can be used for robust inout modifications
SR-7139 Support enforcement of exclusive memory accesses in Release builds
Issue Description:
From the ABI Stability manifesto:
"Another goal of Swift is to improve the applicability of Swift to systems programming. Ownership semantics may make a large impact, including things such as improved inout semantics that allow for efficient and safe array slicing. Providing the right abstractions for efficient use of contiguous memory is still under investigation"
I'm filing this issue to track that work.
The text was updated successfully, but these errors were encountered:
Yes, this was originally on the ABI Dashboard, but we decided to replace it with more specific entries. This one was too vague to be useful. We added a new Ownership section on the dashboard with 6 new entries: SR-7100, SR-7134, SR-7135, SR-7139, SR-7140, and SR-7141.
I don't see much point in keeping this one open now.
Additional Detail from JIRA
md5: 27dc1698347c6a882dd0786c61ce49ca
relates to:
Issue Description:
From the ABI Stability manifesto:
"Another goal of Swift is to improve the applicability of Swift to systems programming. Ownership semantics may make a large impact, including things such as improved inout semantics that allow for efficient and safe array slicing. Providing the right abstractions for efficient use of contiguous memory is still under investigation"
I'm filing this issue to track that work.
The text was updated successfully, but these errors were encountered: