4 ms·
There is an infamous library called dispatch. Someone put together http://www.flotsam.nl/dispatch-periodic-table.html http://www.flotsam.nl/dispatch-periodic-ta
by weego 12y ago
There is an infamous library called dispatch. Someone put together http://www.flotsam.nl/dispatch-periodic-table.html http://www.flotsam.nl/dispatch-periodic-table.html to try and help other developers out when using it. I use it because it is good... but hell. The lack of discipline there is awful.
The problem is that, out in the wild, you're going to end up with legacy code made by people who picked a different sub-set.
This is the situation I've been in for the last year and I agree that for every point I make in praise of language flexibility this is the strongest counter-point.
- oelang 12y agoDispatch was one of the first libraries for scala, it's not really fair to use it as an example. The latest version of dispatch doesn't have that many operators anymore. http://dispatch.databinder.net/Combined+Pages.html http://dispatch.databinder.net/Combined+Pages.html
- chrisloy 12y agoDispatch is a library that I initially found irritating, because in early versions it proved extremely opinionated in it's use of futures and symbolic operators. However, as time has gone on, I've found that my coding style in Scala has evolved to the point where I want low-level libraries to work in an asynchronous way. There are now also overloaded, human-readable methods for most (if not all) of the symbolic operators. These days it is my HTTP client of choice.
- mercurial 12y agoIt's not bad, but they have some work to do to catch up with conduit's operators like $$+-.