Changing the order of type-class constraints on a type signature may break existing Haskell code.
-
-
-
Replying to @aloiscochard2 replies 1 retweet 0 likes
-
Replying to @dibblego
*sad trompet* I don't understand why though, as it is suppose to annotate the type of arguments, right?
1 reply 0 retweets 0 likes -
Replying to @aloiscochard
It's a consequence of stringly-typed programming in stringly programming languages.
1 reply 0 retweets 3 likes -
Replying to @dibblego
I don't see what strings have to do with this. It's about explicit vs implicit.
2 replies 0 retweets 0 likes -
Replying to @mbrcknl
Programming against the hypothetical Haskell AST, instead of a text editor, resolves the matter to non-existence.
1 reply 0 retweets 1 like -
Replying to @mbrcknl
Having to write Scala, and wishing for zero-penalty for circumventing silly ideas, compels this concept, then generalise.
8:01 PM - 14 Jun 2016
0 replies
0 retweets
0 likes
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.