[swift-evolution] Isolated and failable green threads?

[Fabian Balslev Saers]

Hi Brent, Austin and Chris, thank you very much for your quick response,

> On 28 Jan 2016, at 09:31, Brent Royal-Gordon <brent at architechies.com> wrote:
> Mainly, that concurrency is out of scope for Swift 3 (https://github.com/apple/swift-evolution/blob/master/README.md#out-of-scope). Hang in there, though. :^)


Thanks for clarifying, Brent.

> On 28 Jan 2016, at 09:36, Austin Zheng <austinzheng at gmail.com> wrote:
> No idea what validity this has now, if any, but there's an elegant model described in this document: https://github.com/apple/swift/blob/master/docs/proposals/Concurrency.rst <https://github.com/apple/swift/blob/master/docs/proposals/Concurrency.rst>.

Thank you soo much for the link, I had not seen this. I really like what I’m reading here. :-)

> On 28 Jan 2016, at 19:04, Chris Lattner via swift-evolution <swift-evolution at swift.org> wrote:
> Yep: it is a well thought out approach, but it is also certainly not plan of record - it is just an idea - just like the other stuff in docs/proposals.
> I expect concurrency to be a major focus for Swift 4, but we need to get Swift 3 done first. :-)

Absolutely

One part I didn’t understand from the proposal was this:
“Notice that due to rdar://17144340 we still can't mark Arrays and Optionals as copyable”
Could someone explain that to me (I don’t think I have access to that radar)

This document deals with how to make the threads isolated, which I think lays the groundwork for making threads able to be cleaned up if they crash, without taking the system with it. But I didn’t see a proposal of how to deal with this situation. Is there a similar document you could refer me to that deals with this?

Cheers

	Nik
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160129/59ac2ed2/attachment.html>