Alexey Golev

Maybe I'm wrong, but isn't ventilator/sink pattern a better fit for this?

@bmeck sounds like a mission... will research/play around

I implemented Option and Either based on what you did in `fp-ts` and will gladly create a PR (both Option and Either are covered with tests). However I'm not sure...

I think one can alias `flatMap` to `await` if that's more convenient. `flatMap` makes sense because `Promise` (within the lib, not the original JS one) is a monad. Rust has...

@lessp Rust handles async/await as a separate language feature (similar to js). In Reason it's just another monad. This allows for using different implementations for async tasks. As long as...

It should be an intersection type as far as I understand

Are you using the same flow version for both?

It's clearly something to do with versions, the older version had problems with union/intersection types

I like @wokalski solution. It makes sense for partial updates as well. At the moment, unless you use @mhallin solution of passing all values separately you can't really distinguish two...

@ericgj @paldepind the problem with just wrapping XHR is that when we need to POST things or PUT things we'll have to write wrappers for those as well. Which will...