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
-
could you show us ?
https://play.rust-lang.org/?gist=f0e3b04239b0d4a98bb19d0b5a0a3c1a&version=stable … is the example that's bothering me at this exact moment
-
-
This is actually 100% wrong. The hypothetical impl that I mention would always violate the orphan rule. Rust can 100% always say that the first impl doesn't apply. I have no clue why it doesn't use that knowledge.
-
My "I want the opposite of `#[fundamental]`" thing is still useful, but it would apply on traits not types (a local type in as a type parameter to a trait *is* considered local)
End of conversation
New conversation -
-
-
ouch. Wow that's quite hard. And I don't see any easy way to make it better... :/
-
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
- 4 more replies
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.