The #Scala Trap: seems like it provides some utility at first, requires a lot of investment to understand how each part of it is broken.
-
-
Replying to @puffnfresh
Do you know a well-reasoned blog post or article to that end that I could share / reference?
1 reply 0 retweets 1 like -
Replying to @kumbunterland
nah sorry, it's more of just a combination of a 100 different things. This is a start: https://www.reddit.com/r/haskell/comments/1pjjy5/odersky_the_trouble_with_types_strange_loop_2013/cd3bgcu/ …
1 reply 1 retweet 4 likes -
Replying to @puffnfresh @kumbunterland
That was 4 yeas ago, curious how much is still true.
1 reply 0 retweets 0 likes -
Replying to @channingwalton @kumbunterland
we have plugins for type lambdas and some unification changes. That's about it, I think.
1 reply 0 retweets 0 likes -
Oh lord, I periodically remember that "for yield" is kinda structurally typed based on the functions. So many failed compiles and confusion.
1 reply 0 retweets 1 like -
Replying to @seanparsons @puffnfresh and
It happens in parser - no weird typing, just a rewrite to map / flatMap. Translation has some oddities though.
1 reply 0 retweets 0 likes -
Replying to @DavidGregory084 @puffnfresh and
Oh I know where it happens, as that also means you can't capture it with a macro, which is really annoying. That typing is hella weird compared to Haskell as there's no type to it, like you can use it with something that doesn't have flatMap IIRC.
1 reply 0 retweets 0 likes -
Replying to @seanparsons @puffnfresh and
Worse - you have to have map+flatMap but the signature can be different
1 reply 0 retweets 0 likes
Worse, not only *can* you, but it is a "design feature" of the standard library, and others like it.
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.