Denis Frezzato

The problem is that the code compiles with a record as input. `sequenceS` is meant to be used with structures and the code would not compile with an empty structure.

I agree, but I'm not sure there is a trick to prevent this.

> does it also mean it's not meant to be used on dynamically-sized records? Correct. > what does one do for a dynamically-sized records where each value is a monad?...

[IO](https://io.italia.it/) application is using `fp-ts`. - Mobile application: https://github.com/pagopa/io-app; - Backend: https://github.com/pagopa/io-backend. There are other repositories, but these two are the main ones. IO logo: https://io.italia.it/assets/img/io-it-logo-blue.svg

That `curry` function is not type safe (as well as `compose`) [Playground](https://codesandbox.io/s/sparkling-frog-mtnvc?file=/src/index.ts). `fp-ts` had them, but then they were removed because of this issue, so I don't think they would...

I think using `TaskEither` is a better solution, because it signals that the release handler and `bracket` do nothing with whatever is in the `Right` and I'm happy with the...

I could argue that a type variable like that is useless, `unknown` would be equivalent.

The problem is that the type variables are wrongly annotated, it should be `TE.fromIO(() => 1)`. Why did you have to annotate them?

> Were they wrongly annotated in 2.10 too or is this a breaking change? I was saying that they are wrongly annotated in the snippet you posted.

> I've found it easier to persuade teams to adopt the likes of IO and Task by pointing out that they're just thunks, so the cost of backtracking on their...