You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the dogfood test ,clippy is run on itself to make sure its code has no clippy warnings.
During this process, clippy checks all the dependencies as well, however I think this may actually not be needed.
On my system, I can see that checking the unicode-normalization crate using clippy takes 2-3 minutes alone yet a simple "cargo check" of clippy seems to be much faster.
Perhaps we can somehow "cargo check" the dependencies in the dogfood test and only check the actual repo sourcecode using clippy for a decent dogfood speedup?
The text was updated successfully, but these errors were encountered:
During the dogfood test ,clippy is run on itself to make sure its code has no clippy warnings.
During this process, clippy checks all the dependencies as well, however I think this may actually not be needed.
On my system, I can see that checking the
unicode-normalization
crate using clippy takes 2-3 minutes alone yet a simple "cargo check" of clippy seems to be much faster.Perhaps we can somehow "cargo check" the dependencies in the dogfood test and only check the actual repo sourcecode using clippy for a decent dogfood speedup?
The text was updated successfully, but these errors were encountered: