pub struct TomlDetailedDependency<P: Clone = String> {Show 19 fields
pub version: Option<String>,
pub registry: Option<RegistryName>,
pub registry_index: Option<String>,
pub path: Option<P>,
pub base: Option<PathBaseName>,
pub git: Option<String>,
pub branch: Option<String>,
pub tag: Option<String>,
pub rev: Option<String>,
pub features: Option<Vec<String>>,
pub optional: Option<bool>,
pub default_features: Option<bool>,
pub default_features2: Option<bool>,
pub package: Option<PackageName>,
pub public: Option<bool>,
pub artifact: Option<StringOrVec>,
pub lib: Option<bool>,
pub target: Option<String>,
pub _unused_keys: BTreeMap<String, Value>,
}
Fields§
§version: Option<String>
§registry: Option<RegistryName>
§registry_index: Option<String>
The URL of the registry
field.
This is an internal implementation detail. When Cargo creates a
package, it replaces registry
with registry-index
so that the
manifest contains the correct URL. All users won’t have the same
registry names configured, so Cargo can’t rely on just the name for
crates published by other users.
path: Option<P>
§base: Option<PathBaseName>
§git: Option<String>
§branch: Option<String>
§tag: Option<String>
§rev: Option<String>
§features: Option<Vec<String>>
§optional: Option<bool>
§default_features: Option<bool>
§default_features2: Option<bool>
§package: Option<PackageName>
§public: Option<bool>
§artifact: Option<StringOrVec>
One or more of bin
, cdylib
, staticlib
, bin:<name>
.
lib: Option<bool>
If set, the artifact should also be a dependency
target: Option<String>
A platform name, like x86_64-apple-darwin
_unused_keys: BTreeMap<String, Value>
This is here to provide a way to see the “unused manifest keys” when deserializing
Implementations§
source§impl<P: Clone> TomlDetailedDependency<P>
impl<P: Clone> TomlDetailedDependency<P>
pub fn default_features(&self) -> Option<bool>
Trait Implementations§
source§impl<P: Clone + Clone> Clone for TomlDetailedDependency<P>
impl<P: Clone + Clone> Clone for TomlDetailedDependency<P>
source§fn clone(&self) -> TomlDetailedDependency<P>
fn clone(&self) -> TomlDetailedDependency<P>
Returns a copy of the value. Read more
1.0.0 · source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
Performs copy-assignment from
source
. Read moresource§impl<P: Clone> Default for TomlDetailedDependency<P>
impl<P: Clone> Default for TomlDetailedDependency<P>
source§impl<'de, P> Deserialize<'de> for TomlDetailedDependency<P>where
P: Deserialize<'de> + Clone,
impl<'de, P> Deserialize<'de> for TomlDetailedDependency<P>where
P: Deserialize<'de> + Clone,
source§fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>where
__D: Deserializer<'de>,
fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>where
__D: Deserializer<'de>,
Deserialize this value from the given Serde deserializer. Read more
Auto Trait Implementations§
impl<P> Freeze for TomlDetailedDependency<P>where
P: Freeze,
impl<P> RefUnwindSafe for TomlDetailedDependency<P>where
P: RefUnwindSafe,
impl<P> Send for TomlDetailedDependency<P>where
P: Send,
impl<P> Sync for TomlDetailedDependency<P>where
P: Sync,
impl<P> Unpin for TomlDetailedDependency<P>where
P: Unpin,
impl<P> UnwindSafe for TomlDetailedDependency<P>where
P: UnwindSafe,
Blanket Implementations§
source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Mutably borrows from an owned value. Read more
source§impl<T> CloneToUninit for Twhere
T: Clone,
impl<T> CloneToUninit for Twhere
T: Clone,
source§unsafe fn clone_to_uninit(&self, dst: *mut T)
unsafe fn clone_to_uninit(&self, dst: *mut T)
🔬This is a nightly-only experimental API. (
clone_to_uninit
)source§impl<T> Serialize for T
impl<T> Serialize for T
fn erased_serialize(&self, serializer: &mut dyn Serializer) -> Result<(), Error>
fn do_erased_serialize( &self, serializer: &mut dyn Serializer, ) -> Result<(), ErrorImpl>
impl<T> DeserializeOwned for Twhere
T: for<'de> Deserialize<'de>,
Layout§
Note: Unable to compute type layout, possibly due to this type having generic parameters. Layout can only be computed for concrete, fully-instantiated types.