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
Remove proposal IDs from discussion extraction exception list
Remove IDs for proposals with formatting fixes from the exception list
that ignores issues with this field.
Update test snapshot to match latest proposals and new expected results
"summary" : "Swift condition clauses appear in `guard`, `if`, and `while` statements. This proposal re-architects the condition grammar to enable an arbitrary mix of Boolean expressions, `let` conditions (which test and unwrap optionals), general `case` clauses for arbitrary pattern matching, and availability tests. It removes `where` clauses from optional binding conditions and case conditions, and eliminates gramatical ambiguity by using commas for separation between clauses instead of using them both to separate clauses and terms within each clause. These modifications streamline Swift's syntax and alleviate the situation where many Swift developers don't know they can use arbitrary Boolean conditions after a value binding.",
4153
-
"title" : "Restructuring Condition Clauses",
4154
-
"warnings" : [
4155
-
{
4156
-
"code" : 0,
4157
-
"kind" : "warning",
4158
-
"message" : "Discussion link doesn't refer to a Swift forum thread. Discussion removed.",
"summary" : "Swift's distributed actors offer developers a flexible bring-your-own-runtime approach to building distributed systems using the actor paradigm. The initial design of the feature aimed for systems where all nodes of a distributed actor system (such as nodes in a [cluster](https:\/\/github.com\/apple\/swift-distributed-actors)) share the same binary, and therefore all have access to the concrete `distributed actor` declarations which may be resolved and made remote calls on.",
19662
-
"title" : "Resolve DistributedActor protocols",
19663
-
"warnings" : [
19664
-
{
19665
-
"code" : 0,
19666
-
"kind" : "warning",
19667
-
"message" : "Review ended on 2024-03-26 00:00:00 +0000.",
"summary" : "We propose allowing noncopyable fields in deinit-less aggregates to be consumed individually, so long as they are defined in the current module or frozen. Additionally, we propose allowing fields of such an aggregate with a deinit to be consumed individually *within that deinit*. This permits common patterns to be used with many noncopyable values.",
19719
-
"title" : "Partial consumption of noncopyable values",
19720
-
"upcomingFeatureFlag" : {
19721
-
"flag" : "MoveOnlyPartialConsumption"
19722
-
}
19815
+
"title" : "Partial consumption of noncopyable values"
"summary" : "Pattern matching over noncopyable types, particularly noncopyable enums, can be generalized to allow for pattern matches that borrow their subject, in addition to the existing support for consuming pattern matches.",
19868
19961
"title" : "Borrowing and consuming pattern matching for noncopyable types",
"summary" : "This proposal introduces a mutual exclusion lock, or a mutex, to the standard library. `Mutex` will be a new synchronization primitive in the synchronization module.",
"summary" : "The current Swift Package Manager manifest API for specifying Swift language version(s) applies to an entire package which is limiting when adopting new language versions that have implications for source compatibility.",
0 commit comments