Michael Arnaldi

`collect` => `filterMap` I am ok with it but `forEach` => `traverse` I am not because traverse is a different function as it preserves the input structure while forEach accepts...

also I think @schickling intended to mention `collectAll` and not `collect`, so `filterMap` would be a better name for `collect` but `collectAll / tuple` are still variants of the same...

I think it's fine as we have it imho

Amazing thank you!

It seems that it is only partially resolved though, while inference work the signature after `map(typeClass)` is not resolved, that will make all the inferred types painful to use when...

Amazing! Looks great

This currently breaks the encoding used in `@effect/*` for HKTs and probably a few other libraries that rely on the same pattern (hotscript, storybook, come to mind)

> I can confirm that the change in behavior is caused by #53098. We definitely want the deferred resolution implemented by that PR. However, it means that types like `(TTypeLambda...

> I don't think we need to be this dramatic. I see this as an opportunnity to clarify TS team stance on HKT. Community started evolving libraries to take advantage...

We use: ```ts export const f = map(typeClass) ``` and let it derive the type of `f`, with this change the typing of `f` will be impractical to use and...