Gleb
Gleb
I usually use `=copy() .error` and `=sink() .error` for types that are used to communicate between multiple threads (perhaps some foreign) and the object needs to be pinned to a...
@Araq checked out `byref` in the manual, but am still puzzled how this will work in this case. I have some structure that is shared by multiple threads, and is...
Checked out the discussion in #75. Still don't understand how `byref` is relevant. I need `RwLock` to occupy a specific chunk of memory. How will `byref` help with this?
By the way, perhaps the compiler could be patched so that in constructions like ``` var x: T x = fn() ``` or ``` obj.x = fn() ``` the special...
> No, instead `myobj.rwLock = createRwLock()` should compile and treated as a move. The RwLock type needs to be marked with `byref` for this to work. I have a following...
Found some apparent problems with the compiler due to this change, distilled and reported them in nim-lang/Nim#24374 Here the `=destroy`, and hence `tryRecv` can be called with a wrong type...
I don't think this is supposed to work without `--mm:atomicArc`. References are tied to the garbage collector, hence to the thread.