Wayne Van Son

`unsafePerformIO`, alongside `unsafePerformTask`. The implementation leaks, but it's clear that it's an unsafe operation. I find unsafe operations are useful when integrating with other tools that aren't built using `fp-ts`....

This is a great question and response. Can we have this added to the docs under guides? https://gcanti.github.io/fp-ts/guides/

todo: label as docs, implement We should have a list of letters to come next. Currently I've seen for 3.0 we have E1 and E2 when there are duplicates, which...

Make a PR, very useful :) ```diff // ObservableEither.ts export const retry = ( number: number, ): RxJS.OperatorFunction => t$ => t$.pipe( RxJSOperators.mergeMap(t => (Either.isLeft(t) ? RxJS.throwError(t) : RxJS.of(t))), RxJSOperators.retry(number),...

@OliverJAsh I don't think we need to implement them specifically, unless they're not pipeable. We can just use them in the `pipe` operator as they are.

How did we go on this one? Switch map is important. Otherwise I may have to maintain a patched version of this repo if I am to use chain in...

> ```ts > const fold = (obs: Observable) => > observable.chain(t => from(t))(obs); > ``` @pbadenski `fold` Is an unsafe cast. Perhaps just use `map(a => a as Observable)`. `fromTask`...

If users are willing to coerce using functions like we do in FP languages, then it shouldn't be a problem. Personally I'm for it, as long as the coercion functions...

It brings it more in line with Purescript. It makes effect only monads more clear. When I was starting out with `fp-ts` designing some API's, I didn't realise that we...

Assuming we are using monadic composition, the trade off isn't too bad. We can treat it just like a type, because we don't need to unwrap it at all because...