My least favorite trend on Rust RFCs are people who make arguments assuming that Rust will eventually become Haskell. Arguments like "what about HKT" or "consider monoids, semigroups, etc" or "this might confuse haskell programmers" are just so out of place.
-
Similar happening in JS with both OOP and FP developers fighting each for their popular features which *obviously* should be added to JavaScript.
I have no problem with FP concepts being added to Rust. But we should not evaluate RFCs today based on the assumption that we will eventually be Haskell
-
-
I'd still substitute "Rust" and "Haskell" with any other pair of langs.
-
Ironically I had a long argument at work with someone trying to turn Ruby into Rust. I think there's a pattern
End of conversation
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.