Re: Nim v1.1 and beyond roadmap

[Araq]

@GordonBGood The legacy code is bad, I know. It's also "just" something we need 
to sort out. Much more problematic to me is that neither `owned` nor `dispose` 
can handle async's complexities which is _the_ most important requirement for 
us. If we cannot solve this problem, using the tracing GC aspect just for this 
would be valid option but then how can move the task/continuation to a 
different thread. It's like we want a _thread-local_ GC on top of a _shared_ 
memory allocator... More thinking and experiments are required. ;-)