> cases where I think it is necessary to annotate Worth noting that that can be reactive, too. If an type checking error message is confusing or insufficientl

> cases where I think it is necessary to annotate Worth noting that that can be reactive, too. If an type checking error message is confusing or insufficiently localized, pinning down a few things around it can clarify. As tome says, though, that can be a thing in Haskell too. There exist situations in Haskell where the compiler cannot figure out the types for you, but they're not most code.