You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
No need to type check implementation files when an .fsi file exists #10201
Will has the details, and can fill this out more. There is a tremendous peformance gain when we don't typecheck implementation files that are not open.
Reacted by Vlad Zarytovskii, Abel Braaksma and Heron Barreto Peixoto
changed the title [-]No need to type check implementation files when an FSI file exists[/-][+]No need to type check implementation files when an .fsi file exists[/+]on Sep 30, 2020
@heronbpv, I'm with you, I don't like them when creating apps, however, if you are creating libraries for public consumption, they are very useful for controlling the visibility of the types and functions in the libraries.
Reacted by Saul Rennison and Heron Barreto Peixoto
Activity
[-]No need to type check implementation files when an FSI file exists[/-][+]No need to type check implementation files when an .fsi file exists[/+]abelbraaksma commentedon Sep 30, 2020
This would help sooooo much in large projects wrt tooling perf, and would be an extra benefit for adding fsi files (I usually don't).
smoothdeveloper commentedon Oct 1, 2020
Waiting for this optimization to land before opening again TypeChecker.fs 😄.
heronbpv commentedon Oct 1, 2020
This. Never saw any reason to make a .fsi file, until now. Always seemed like redundant work.
KevinRansom commentedon Oct 1, 2020
@heronbpv, I'm with you, I don't like them when creating apps, however, if you are creating libraries for public consumption, they are very useful for controlling the visibility of the types and functions in the libraries.