> And i don't recommend to use asyncdispatch because you will fall into lot of > bugs, leaks and problems.
Please provide some links to these bugs, leaks and problems. Asyncdispatch is the foundation of chronos. Sure, maybe you've fixed some edge cases, but you've also broken the API and indeed are not compatible with most async Nim packages. Asyncdispatch has also continued to evolve and I'm sure there are things that have been fixed there that haven't been fixed in Chronos. Instead of spending your efforts telling users to use chronos and hurting our community, why don't you instead upstream some of these fixes you've made? Asyncdispatch isn't going anywhere, it will remain in Nim 1.0 and beyond. > It is complicated at this time to use the asyncdispatch as it has several > issues that have not been solved over time. In what way is it complicated? Can you share some examples?
