[swift-evolution] Contiguous Memory and the Effect of Borrowing on Safety
davesweeris at mac.com
Sat Nov 12 18:19:34 CST 2016
> On Nov 10, 2016, at 12:39 PM, Stephen Canon via swift-evolution <swift-evolution at swift.org> wrote:
>> On Nov 10, 2016, at 1:30 PM, Dave Abrahams via swift-evolution <swift-evolution at swift.org> wrote:
>> What worries me is that if systems programmers are trying to get static
>> guarantees that there's no ARC traffic, they won't be willing to handle
>> a copyable thing that carries ownership.
> FWIW, we (frequently) only need a static guarantee of no ARC traffic *within a critical section*. If we can guarantee that whatever ARC operations need to be done happen in a precisely-controlled manner at a known interface boundary, that’s often good enough.
“Critical section” is a phrase I normally associate with multi-threaded code… Do we need to start talking about concurrency to move this topic forward?
- Dave Sweeris
More information about the swift-evolution