You just gave me a half baked idea. If `rustc` encounters >N parse errors, it should just stop and avoid trying to continue to the type checker.
When your refactoring causes so many errors that your "compile time" is limited by lock contention on stderr printing all the compiler errors
-
-
-
In general I wish rustc would stop earlier. We have `impl<T: Expression> AsExpression<T::SqlType> for T` in Diesel. If Rust encounters a case where `AsExpression<SomeType>` isn't implemented, it assumes that the blanket impl applies, and spits out 4 more errors 1/2
- 13 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.