Issue 12090 - Make std.concurrency compatible with fibers as threads

https://d.puremagic.com/issues/show_bug.cgi?id=12090
My point still stands:
> As a user reading this, I'd wonder what a logical thread is, and how it relates to the term "asynchronous context" used elsewhere in the documentation.

At least in my eyes, "logical thread" is not a clearly defined term, but different platforms and concurrency APIs use it in slightly different ways. Elsewhere in this module, you talk about starting things in an "asynchronous context", which, as far as I can see, refers to the same thing. So, I'd say either change all places to use "logical thread", or define the terms somewhere. Everything else will cause confusion.

To put it differently, my comment was not about the name "logical thread" itself, but rather the fact that the terminology doesn't seem to be consistent throughout the module. A user should be able to infer what they are dealing with from reading the documentation without having to hope they guessed the definitions right. I don't think we are quite there yet.

The fact that the top-level comment still asserts that
> Right now, only in-process threads are supported and referenced by a more specialized handle called a Tid. It is effectively a subclass of Cid, with additional features specific to in-process messaging."

while Tids now can represent specific fibers doesn't exactly help with that either.