3 ms·
> Type inference is very convenient, so there's no need to do this universally - however, it can be a useful thing to try if you've identified a slow section of
by kostarelo 6y ago
> Type inference is very convenient, so there's no need to do this universally - however, it can be a useful thing to try if you've identified a slow section of your code.
Can we actually identify which piece takes longer to compile?
- nandi95 6y agoI think you can in 4.1 add --generateTrace and the output path. The result you can inspect in the browser. Also there's -- extendedDiagnistics if I remember correctly that tells you which part of the compilation process takes what time