blackmius
blackmius
I dont know if it is related or i need to create another issue. I found that generic proc arguments cannot be lifted in continuation. for example ```nim proc a(n:...
i imagined it different, it still uses sort of ioqueue but there is no wait and events, io_uring did it all under the kernel. As we dont need to wait...
i made a small experiment to showcase what changes can be made to adopt io_uring https://github.com/blackmius/nim-sys (last 2 commits)
sure `seq` -> `set`, sorry for confusion
doesnt it means that type T is not simple anything, but have to implement init proc? maybe go to finalising `concept` way ```nim type A = concept a a.init() is...
add tests where you passing lambda functions into coroutine, tests calling coroutine inside other coroutine (or you designed it to call `launch` in all cases?), and running lambdas inside coroutines...
also how try/except/finally and defer will work in coroutines?
@zerbina i suggested such tests because there were problems with these cases in CPS and async/await implementations. > Closures returning coroutines work just like any other closure. As for a...
suspend lifted differently than yield, maybe it is better to check these cases too ```nim proc a() {.coroutine.} = for i in 1..5: echo i suspend(self) var q = 5...
while i thinking of how to add supporting for return types i think come with such design ``` nim let router = newRouter() type MyEnum = enum A B C...