Fiber and Thread Communication

[Ali Çehreli via Digitalmars-d-learn]

On 04/08/2016 01:16 PM, Dicebot wrote:
> On Friday, 8 April 2016 at 19:46:17 UTC, tcak wrote:
>> On Friday, 8 April 2016 at 15:33:46 UTC, Dicebot wrote:
>>> On Friday, 8 April 2016 at 14:08:39 UTC, Nordlöw wrote:
>>>> So a TId can represent either a thread or a fiber?
>>>
>>> AFAIR, yes (I haven't used std.concurrency in a long while, telling
>>> all from memory only).
>>
>> yes what? Thread or Fiber.
>
> Yes both :) Tid represent abstract execution context, with no
> implications about underlying executor.

Thanks Dicebot. I don't think the included 
std.concurrency.FiberScheduler has support for message passing because 
FiberScheduler.spawn does not return a Tid. If so, I don't see how it's 
possible to send messages between fibers.

Ali