Mirror of forum.nim-lang.org

5262 :: Bad design of coro library.

• japplegame (orginal) [2019-10-02T10:44:04+02:00] view original

  I think standart coro library has a bad design. Implementations of coroutines and scheduler should be separated from each other. With the current implementation it is impossible to write custom scheduler.

---

• mratsim (orginal) [2019-10-02T10:55:05+02:00] view original

  Feel free to fork it as a package.

  It's currently working but not really maintained and not an alternative to async at the moment.

  But are there any coroutines/fibers libraries with a separated scheduler?

---

• japplegame (orginal) [2019-10-02T11:49:39+02:00] view original

  But are there any coroutines/fibers libraries with a separated scheduler?

  D, Ruby, C++ (Boost.Coroutine2) have a scheduler-independent coroutine implementations.

---