I have some really terrible examples from early Stylo days that I should scrounge up, where the type parameters are all entangled
-
-
Replying to @ManishEarth @yaahc_ and
I had some examples from Diesel that I used to think were horrible until I saw some open source code that... Was extremely generic.
2 replies 0 retweets 6 likes -
Replying to @sgrif @ManishEarth and
i don’t know if i really think this kind of code is “bad”...it’s saying a lot, when you think about it!
2 replies 0 retweets 4 likes -
also, of the fairly small handful of languages that even let you *express* this kind of type constraints, rust’s syntax for it is the most readable by far
2 replies 0 retweets 9 likes -
-
Replying to @sgrif @ManishEarth and
hot take: `=>` is the least obvious syntax in all of haskell
3 replies 0 retweets 6 likes -
scala has this ability for people to override and redefine operators. Also what's wrong with the fish operator `><>` ? Isn't it lovely?
2 replies 0 retweets 0 likes -
I still have nightmares about trying to read other folks SBT files, not recognizing an operator, and basically having no way to look it up. You can't google random punctuation
1 reply 0 retweets 6 likes -
Also why the fuck does every Scala lib think that ~> is a meaningful operator that they need to override with a new meaning
1 reply 0 retweets 3 likes -
yeah, they should all consider using `>@>`. It makes much more sense.
1 reply 0 retweets 0 likes
Dancing kirby is the best operator and we all know it
@rustlang when are we getting std::ops::DancingKirby
-
-
Be the April first RFC you wish to see in the world
2 replies 0 retweets 4 likes -
Nah I already have something much bigger planned this year
1 reply 0 retweets 9 likes - 1 more reply
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.