Give an explanation for exempting implicit_hasher

This commit is contained in:
Dale Wijnand 2018-07-23 07:46:05 +01:00
parent a8e3827e98
commit 8dc00d45c1
No known key found for this signature in database
GPG Key ID: 4F256E3D151DF5EF
2 changed files with 4 additions and 2 deletions

View File

@ -106,7 +106,8 @@ mod types;
///
/// * `print_warnings` - whether or not to print backwards-compatibility
/// warnings and such
#[cfg_attr(feature = "cargo-clippy", allow(implicit_hasher))] // exempted
// While unfortunate, generalising this over different hashers would be a large project
#[cfg_attr(feature = "cargo-clippy", allow(implicit_hasher))]
pub fn resolve(
summaries: &[(Summary, Method)],
replacements: &[(PackageIdSpec, Dependency)],

View File

@ -133,7 +133,8 @@ fn resolve_with_registry<'cfg>(
///
/// The previous resolve normally comes from a lockfile. This function does not
/// read or write lockfiles from the filesystem.
#[cfg_attr(feature = "cargo-clippy", allow(implicit_hasher))] // exempted
// While unfortunate, generalising this over different hashers would be a large project
#[cfg_attr(feature = "cargo-clippy", allow(implicit_hasher))]
pub fn resolve_with_previous<'a, 'cfg>(
registry: &mut PackageRegistry<'cfg>,
ws: &Workspace<'cfg>,