When your refactoring causes so many errors that your "compile time" is limited by lock contention on stderr printing all the compiler errors
-
I've got an RFC I'm writing to provide an attribute which can be placed on impls to tell rustc "Please do not recommend this impl". Explicit annotation is the only fix in this case I think. My desired behavior in *this* case is "Follow the impl chain to N-1 places"
This would also help in cases where you want Rust to recommend another impl, but it doesn't because there are two "possible" cases that could apply (even though one never does)
-
-
There's a few cases like that in Diesel right now, and they're the difference between "<3 page long type>: ExecuteDsl is not satisfied" and "String: FromSql<Integer> is not satisfied"
-
It does sound like an annotation with "similar" behavior to `rustc_on_unimplemented` would be enough for your case, but it'd be nice if rustc had better behavior for this case by default (I want to minimize how many hints library writers need to add for us to do the right thing).
- 7 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.