Mirror of forum.nim-lang.org

8603 :: Supporting both chronos and asyncdispatch in async code

• arnetheduck (orginal) [2021-11-08T12:01:21+01:00] view original

  For a while now, we've relied on chronos to deliver async/await capabilities to our little world of peer-to-peer applications - it is stable, secure and in active development.

  On top of chronos, we build various libraries and components, and some of these may want to support both chronos, asyncdispatch and future async libraries, should demand arise for more.

  I'm happy to see that https://github.com/nim-lang/Nim/pull/18700/ has been merged providing two "standard" ways of adding this support - either side-by-side or application-wide:

  • for side by side, nim-metrics provides a model implementation: depending on which framework your application is based on, you import one module or the other - this is a powerful way of supporting both frameworks because it's easier to compose and add to an existing application
  • for libraries that don't lend themselves to this model, a global flag model exists instead - this has the obvious downside that it works poorly for composing libraries (specially deep down in a transitive dependency tree) but is a pragmatic choice to get started with.

  Happy coding and thanks to yglukhov for suggesting it ;)

---