On the one hand, I have many legitimate use cases for higher kinded types in Rust and I hope they land soon. On the other, I'm extremely worried about how they would affect the Rust ecosystem once everyone starts trying to implement Haskell style category theory libraries.
-
Show this thread
-
I think the hardest lesson I've learned over the past year and a half of Rust development is that "this is good in Haskell" rarely implies "this is good in Rust," despite the surface similarities between the languages. Not sure everyone would learn that lesson in time...
4 replies 6 retweets 39 likesShow this thread -
Bodil Stokke, Esq. Retweeted Bodil Stokke, Esq.
I mean, re: https://mobile.twitter.com/bodil/status/1027316997904891904 … - that was a joke and I actually took lenses _out_ of http://immutable.rs because in the end I couldn't see the point of them, where the use case in Haskell (and Clojure) is obvious.
Bodil Stokke, Esq. added,
1 reply 1 retweet 15 likesShow this thread -
On the other hand, I really do think Rust would benefit greatly from a simple Monad interface so we could have fully generalised do notation instead of this async/await silliness.
6 replies 3 retweets 30 likesShow this thread -
Replying to @bodil
I dunno, I think I'd rather a zero-cost version of an effect system (if that is possible). But I think that ship has very much sailed :(
1 reply 0 retweets 0 likes -
Replying to @brendanzab @bodil
@canndrew had some proposals to that (kuhumm) effect. I think the biggest part of the issue here is that nobody has done this _before_ and the "no new research" principle. (Which the name "Rust" may or may not bear some relation to.)1 reply 0 retweets 1 like -
Replying to @glaebhoerl @brendanzab and
(Also like Graydon's story about why Rust ended up with type classes (paraphrasing from memory): there were people on the team who knew how to implement type classes, there weren't people on the team who knew how to implement the latest fancy module systems research.)
2 replies 0 retweets 1 like
Yeah, as I recall nobody was advocating for ML-style modules, but @MarijnJH really wanted typeclasses. So we got typeclasses. (The right decision IMO; they’re easy to use and well-understood.)
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.