A modern programming language that makes developers happier.

kotlinlang

This pr is now pretty much done: <https://github.com/arrow-kt/arrow-fx/pull/270> A review is much appreciated.
This brings software transactional memory to arrow with quite a few datatypes already implemented.

I don't think we should put STM in the main module, and I think we should split off Stream actually.

There is no strong reason to have Stream in the same module, and a lot of coroutines users won't need Streams.

While I do agree it should split, I am kind if worried about how docs work and how discoverable it'll be. If there is a good solution to both of those then I'll change it right away

I think we can split in a separate pr and have the main fx artifact bundle all of them

Should not impact docs since the menu can be pointed to any location of modules in the docs