Malte Legenhausen

@gcanti I tried to replace all `sequenceS` calls in a bigger codebase and there are two points I would like to address when deprecating `sequenceS`. 1. ~~We would need `DoSeq`...

This can actually not be fixed without moving/duplicating `sequenceS` to `Applicative` else we are not able to return an empty instance via `F.of({})`. With the deprecating in mind I don't...

Company name: werk85 SVG Logo: [logo-werk85.zip](https://github.com/gcanti/fp-ts/files/4159859/logo-werk85.zip) Webseite: https://werk85.de Github: https://github.com/werk85 We use it for all our front and backend application. All private repos. A framework we are currently using for...

When playing around with this case it becomes even more crazy. When we generalize the problem to `input = separator` we should actually return `['', '']` 😉 ```ts 'a'.split('a') ===...

@asherccohen if you want to take a look at `ixjs` there is also the wrapper library [fp-ts-ixjs](https://github.com/werk85/fp-ts-ixjs).

If we choose `chainFirst` as reference we should actually use a new generic variable that is not used in the result or should align all `First` function to use `unknown`....

IMHO default exports are an anti pattern. They make importing a module, enforcing naming conventions and refactorings harder.

Looks good. Just another idea when creating a `Bound` why not have a function that always returns a valid bound like your `fromRange` but one that never fails. ```ts export...

Use case for me would be as smart constructor where I do not care about validation and just want a valid `Bounded`. I find `isSingular` a good choice.

I like the idea of a `run` function but only for `IO` and `Task`. This `run` function can indicate that you are about to leave your pure implementation and execute...