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
The current cargo check architecture (#3296) always uses rmeta files, even if an rlib is available, that means that if the rlib doesn't need to be rebuilt, then work is wasted. It would be good to use the rlib if possible.
This is a bit complex because:
we specify the file in an --extern arg to rustc, therefore we need to know which to use,
even if the rlib is fresh, one of its dependencies might not be, causing it to be rebuilt, if that happens we should just build an rmeta, not an rlib,
we therefore don't know until after the crate is built whether we should pass the rmeta or rlib using --extern
that info is not easily available in Cargo right now.
The text was updated successfully, but these errors were encountered:
The current cargo check architecture (#3296) always uses rmeta files, even if an rlib is available, that means that if the rlib doesn't need to be rebuilt, then work is wasted. It would be good to use the rlib if possible.
This is a bit complex because:
--extern
arg to rustc, therefore we need to know which to use,--extern
The text was updated successfully, but these errors were encountered: