Preventing Data Races in the Swift Concurrency Model

[masters3d]

Are state races also in scope? I’m thinking about the kind of state races that are introduce with actor reentrancy. If so then it would be great if actors had the ability to distinguish between mutating (read-write) and non-mutating (read-only) methods like we do for structs/enums.

SE-0296: async/await

I'm not sure if it helps, but I see "async/await vs actors" to be analogous to "closures/functions and struct methods". Functions/closures in Swift can capture arbitrary state, are great at expressing a single action performed against a bag of state, and you can technically define families of them to do things if you try hard enough. However, this quickly becomes a pain when the state you manage is the primary thing, and the actions implemented against that state grow over time. To solve this…

This would allow us to default to reentrancy in non-mutating methods and default to non-reentrancy in mutating methods. This would compose nicely if all stored properties in an actor are enforced to be shareable.