3 ms·
I think Haskell gets this close to right, actually. If always adding the type to every function is always better, I can do that. But as it turns out, occasion
by dllthomas 3y ago
I think Haskell gets this close to right, actually. If always adding the type to every function is always better, I can do that. But as it turns out, occasionally during development looser error locations if I hit a relevant error is a reasonable price to pay for not having to update a signature or two while I iterate. Haskell community norms say you should annotate top level functions before you share the code, and any particular team can make that stricter. I don't think there's actually a good reason to require it on every single build regardless of the purpose of that build.