Invalid type inference when using arrow function but normal functions is ok

Bug Report

🔎 Search Terms

Invalid type inference with arrow function

🕗 Version & Regression Information

• This changed between versions @effect/io^0.30 and @effect/io>=0.31. The main change that I suspect is causing the bug is this commit.

⏯ Playground Link

At least, playground cannot import third-party lib(effect). so here, I provide some stackblitz links:

• @effect/io <=0.30 + TS 5.1: https://stackblitz.com/edit/typescript-qiykfu (This is what I think is actual behavior)
• @effect/io ^0.32 + TS 5.1: https://stackblitz.com/edit/typescript-wjbz9s
• @effect/io ^0.32 + TS 5.2 (dev, next channel): https://stackblitz.com/edit/typescript-tbg3w8

💻 Code

🙁 Actual behavior

If you write it as a regular function expression, the type is inferred without any problems. but writing in arrow function expressions causes problems with type inference.

🙂 Expected behavior

In the same way that the Effect library works, the resolve function should be correctly typed by inferring the dependencies passed through the effect object, the type of the required objects, and the way the function is written. There should be no difference in the way the resolve function is written.

Beginne damit, die drei StackBlitz-Reproduktionen zu vergleichen, und untersuche den im Bericht verlinkten verdächtigen @effect/io-Commit. Konzentriere dich dabei auf die Änderung, die die Inferenz betrifft. Bestätige das Verhalten für äquivalente Formen regulärer Funktionen und Pfeilfunktionen; als abgeschlossen gilt die Aufgabe, wenn die Pfeilform resolve aus den Effect-Abhängigkeiten und den erforderlichen Objekttypen auf dieselbe Weise ableitet.