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
Cargo wants to be in control of deciding which version of a crate to link to, not rustc. Under the current cargo design, rustc does not need to know about version numbers at all except to frob the symbol hashes a bit. If rustc no longer knows about versioning, then it needs to provide some mechanism for mixing versioning metadata into the version hashes.
The text was updated successfully, but these errors were encountered:
This is an implementation of [RFC 35](https://github.com/rust-lang/rfcs/blob/master/active/0035-remove-crate-id.md).
The summary for this PR is the same as that of the RFC, with one addendum:
* Removes the `#[crate_id]` attribute and knowledge of versions from rustc.
* Added a `#[crate_name]` attribute similar to the old `#[crate_id]` attribute
* Output filenames no longer have versions or hashes
* Symbols no longer have versions (they still have hashes)
* A new flag, `--extern`, is used to override searching for external crates
* A new flag, `-C metadata=foo`, used when hashing symbols
* [added] An old flag, `--crate-name`, was re purposed to specify the crate name from the command line.
I tried to maintain backwards compatibility wherever possible (with warnings being printed). If I missed anywhere, however, please let me know!
[breaking-change]
Closes#14468Closes#14469Closes#14470Closes#14471
cc #14470
Cargo wants to be in control of deciding which version of a crate to link to, not rustc. Under the current cargo design, rustc does not need to know about version numbers at all except to frob the symbol hashes a bit. If rustc no longer knows about versioning, then it needs to provide some mechanism for mixing versioning metadata into the version hashes.
The text was updated successfully, but these errors were encountered: