Changing the order of type-class constraints on a type signature may break existing Haskell code.
-
wtf ! Example?
-
-
*sad trompet* I don't understand why though, as it is suppose to annotate the type of arguments, right?
-
It's a consequence of stringly-typed programming in stringly programming languages.
- Show replies
New conversation -
-
-
so now we should always use explicit forall, because refactoring reasons?
-
We could consider TypeApplications to just be a bad idea for maintainability and move on with our lives.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.