Performance benchmark

[alirezanet]

Hi,
I really liked this idea but people probably don't start using it until they are aware of possible overheads (if has any). personally, after a quick look into this, it brought a lot of questions to my mind. how it performers and what is the cost of using it (because the overhead of state machine and async/await is not so small at least for tasks). can you provide some information or benchmarks that show the performance comparisons?

[yuretz]

Thank you for sharing your thoughts! Generally, I like the idea of including "Performance" chapter in the docs, explaining general performance expectations and considerations.

I'm not sure though, whether benchmarking it directly would add too much value, but I'm afraid it has a potential to be misleading. Also, what to compare it to? Other monadic libraries? Async tasks? I don't know if performance is the biggest concern/motivation for people considering libraries such as this one. The primary use case here is to provide a pure, functional abstraction layer on top of things like filesystem operations, DB queries, HTTP calls and such, which are themselves the slowest part of any app. Of course, it's pretty obvious that abstractions and indirections have their cost, but this cost is almost certainly minimal compared to the cost of performing the I/O itself.

That being said, I'm super grateful for your feedback and agree that performance needs to be addressed one way or the other, I'll just have to think on how to do it in a good way.