David Chambers

I too am keen to merge the two projects. There are significant organizational changes in progress in the various Sanctuary repositories, but I hope to revisit this in a month...

Do you find yourself doing something like this? ``` javascript fut.fork(err => { // do X... // do Z... }, val => { // do Y... // do Z... });...

What are you suggesting, exactly? Something like this? ``` javascript fut.forkFinally(err => { // do X... }, val => { // do Y... }, () => { // do Z......

The idea seems reasonable, but it makes the type signature pretty messy: ``` Future#fork :: Future a ~> (Error -> ()) -> (a -> ()) -> { finally :: ()...

We should certainly hook up Travis CI or CircleCI. :thumbsup:

Does all the code need to live in `main`, @kwijibo? I ask because we already have lots of examples of approaches which fail to separate the pure transformations from the...

I appreciate the pull request, @kwijibo. I'd like to avoid reaching the point where there are dozens of examples which do not satisfy the requirements distracting from the one or...

> While Fluture seems much more mature and complete than our Future I wouldn't want to switch unless it has parallel execution in `ap`. According to fantasyland/fantasy-land#179 a Monad's `fantasy-land/ap`...

This strikes me as a valid concern, @TheLudd. Let's raise the issue with all N of the JavaScript Future/Task library maintainers. :stuck_out_tongue_winking_eye:

> Should we perhaps also consider removing the Either and Maybe from Sanctuary and promote the existing Fantasy Land equivalent packages? Merging the Sanctuary implementations into their respective fantasy-land packages...