[][src]Struct cargo::core::compiler::Metadata

pub struct Metadata(_);

The Metadata is a hash used to make unique file names for each unit in a build. It is also use for symbol mangling.

For example:

  • A project may depend on crate A and crate B, so the package name must be in the file name.
  • Similarly a project may depend on two versions of A, so the version must be in the file name.

In general this must include all things that need to be distinguished in different parts of the same build. This is absolutely required or we override things before we get chance to use them.

It is also used for symbol mangling, because if you have two versions of the same crate linked together, their symbols need to be differentiated.

We use a hash because it is an easy way to guarantee that all the inputs can be converted to a valid path.

This also acts as the main layer of caching provided by Cargo. For example, we want to cache cargo build and cargo doc separately, so that running one does not invalidate the artifacts for the other. We do this by including CompileMode in the hash, thus the artifacts go in different folders and do not override each other. If we don't add something that we should have, for this reason, we get the correct output but rebuild more than is needed.

Some things that need to be tracked to ensure the correct output should definitely not go in the Metadata. For example, the modification time of a file, should be tracked to make a rebuild when the file changes. However, it would be wasteful to include in the Metadata. The old artifacts are never going to be needed again. We can save space by just overwriting them. If we add something that we should not have, for this reason, we get the correct output but take more space than needed. This makes not including something in Metadata a form of cache invalidation.

You should also avoid anything that would interfere with reproducible builds. For example, any absolute path should be avoided. This is one reason that RUSTFLAGS is not in Metadata, because it often has absolute paths (like --remap-path-prefix which is fundamentally used for reproducible builds and has absolute paths in it). Also, in some cases the mangled symbols need to be stable between different builds with different settings. For example, profile-guided optimizations need to swap RUSTFLAGS between runs, but needs to keep the same symbol names.

Note that the Fingerprint is in charge of tracking everything needed to determine if a rebuild is needed.

Trait Implementations

impl Clone for Metadata[src]

impl Copy for Metadata[src]

impl Debug for Metadata[src]

impl Display for Metadata[src]

impl Eq for Metadata[src]

impl Hash for Metadata[src]

impl Ord for Metadata[src]

impl PartialEq<Metadata> for Metadata[src]

impl PartialOrd<Metadata> for Metadata[src]

impl StructuralEq for Metadata[src]

impl StructuralPartialEq for Metadata[src]

Auto Trait Implementations

Blanket Implementations

impl<T> Any for T where
    T: 'static + ?Sized
[src]

impl<T> Borrow<T> for T where
    T: ?Sized
[src]

impl<T> BorrowMut<T> for T where
    T: ?Sized
[src]

impl<T> From<T> for T[src]

impl<T, U> Into<U> for T where
    U: From<T>, 
[src]

impl<T> Same<T> for T

type Output = T

Should always be Self

impl<T> ToOwned for T where
    T: Clone
[src]

type Owned = T

The resulting type after obtaining ownership.

impl<T> ToString for T where
    T: Display + ?Sized
[src]

impl<T, U> TryFrom<U> for T where
    U: Into<T>, 
[src]

type Error = Infallible

The type returned in the event of a conversion error.

impl<T, U> TryInto<U> for T where
    U: TryFrom<T>, 
[src]

type Error = <U as TryFrom<T>>::Error

The type returned in the event of a conversion error.

impl<V, T> VZip<V> for T where
    V: MultiLane<T>,