It's funny seeing people from Ruby rave about how good Rust's error messages are when I know 1000 ways to make it give garbage errors (and I'm running into all of them today). When they're good, they're *really* good, but when they're bad they're... Actually not any worse than rb
-
-
-
Replying to @radiothomas_
https://play.rust-lang.org/?gist=f0e3b04239b0d4a98bb19d0b5a0a3c1a&version=stable … is the example that's bothering me at this exact moment
2 replies 0 retweets 0 likes -
Replying to @sgrif
ouch. Wow that's quite hard. And I don't see any easy way to make it better... :/
1 reply 0 retweets 0 likes -
Replying to @radiothomas_
I think the best way to make it better is to add an annotation you can place on a type parameter to say "a local type in this parameter does not make this type considered local". I should probably write an RFC for that at some point, I'm not sure what a good interface for it is
1 reply 0 retweets 0 likes -
Replying to @sgrif
It could also apply to the type as a whole rather than individual parameters (that probably makes more sense here). But ultimately what I want is something that is exactly the opposite of `#[fundamental]` on types
1 reply 0 retweets 0 likes -
No, the opposite of the fundamental attribute. https://github.com/rust-lang/rfcs/blob/master/text/1023-rebalancing-coherence.md …
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.