> On May 12, 2017, at 19:29, Ben Cohen via swift-evolution > <swift-evolution@swift.org> wrote: > > Hello Swift community, > > The review of revisions to SE-0176: Enforce Exclusive Access to Memory begins > now and runs through May 17, 2017. > > Most of this proposal was previously accepted. An implementation issue has > been discovered with the use of dynamic enforcement on inout parameters. The > proposal implementors suggest adopting a stronger rule governing the use of > non-escaping closures which will also allow Swift to make firm guarantees > about the use of static enforcement when a variable does not escape. The > core team tentatively supports this new rule but believes it is a substantial > enough revision that it requires a separate review period. > The proposal is available here: > https://github.com/apple/swift-evolution/blob/master/proposals/0176-enforce-exclusive-access-to-memory.md >
This subject is a bit over my head, but from what I do understand, +1 - Dave Sweeris
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
