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
Compiling a crate in incremental mode with an empty cache is often slower than compiling the crate non-incrementally. Also, the generated binary is likely to exhibit worse runtime performance and the IC cache for the crate takes up space on disk. At the same time, having a non-incrementally compiled dependency does not have any detrimental effects on incremental compilation as long as that dependency does not change. For these reasons it makes sense to always compile things coming from crates.io or other external sources in non-incremental mode.
The text was updated successfully, but these errors were encountered:
Such a change would likely go here and have an extra check for path sources. Users can only modify path sources, all others should be frozen in Cargo's cache somewhere.
…lexcrichton
Only compile user-modifiable projects incrementally.
Fixes#3972. Thanks for pointing me to the correct implementation, Alex!
r? @alexcrichton
Compiling a crate in incremental mode with an empty cache is often slower than compiling the crate non-incrementally. Also, the generated binary is likely to exhibit worse runtime performance and the IC cache for the crate takes up space on disk. At the same time, having a non-incrementally compiled dependency does not have any detrimental effects on incremental compilation as long as that dependency does not change. For these reasons it makes sense to always compile things coming from crates.io or other external sources in non-incremental mode.
The text was updated successfully, but these errors were encountered: