As much as I admire you for being able to produce this that does compile, no sane human can consume this API.
-
-
Sometimes complex impls are in service of minimal APIspic.twitter.com/Q1jBHtfbBv
3 replies 0 retweets 11 likes -
Yeah, having APIs like this with lots of *independent* generic parameters is NBD imo pretty easy to use, most folks define a type alias if they need to name the type a lot but only use one impl
1 reply 0 retweets 8 likes -
Replying to @ManishEarth @yaahc_ and
I have some really terrible examples from early Stylo days that I should scrounge up, where the type parameters are all entangled
1 reply 0 retweets 3 likes -
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 -
the equals-greater operator
1 reply 0 retweets 7 likes
That is a hashrocket
5:52 PM - 10 Feb 2020
0 replies
0 retweets
5 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.