cargo-0.49.0/src/bin/cargo/cli.rs:7:5: usage of wildcard import
cargo-0.49.0/src/bin/cargo/commands/bench.rs:1:5: usage of wildcard import
cargo-0.49.0/src/bin/cargo/commands/bench.rs:76:59: redundant closure found
cargo-0.49.0/src/bin/cargo/commands/build.rs:1:5: usage of wildcard import
cargo-0.49.0/src/bin/cargo/commands/check.rs:1:5: usage of wildcard import
cargo-0.49.0/src/bin/cargo/commands/clean.rs:1:5: usage of wildcard import
cargo-0.49.0/src/bin/cargo/commands/doc.rs:1:5: usage of wildcard import
cargo-0.49.0/src/bin/cargo/commands/fetch.rs:1:5: usage of wildcard import
cargo-0.49.0/src/bin/cargo/commands/fix.rs:1:5: usage of wildcard import
cargo-0.49.0/src/bin/cargo/commands/generate_lockfile.rs:1:5: usage of wildcard import
cargo-0.49.0/src/bin/cargo/commands/git_checkout.rs:1:5: usage of wildcard import
cargo-0.49.0/src/bin/cargo/commands/help.rs:20:1: item name ends with its containing module's name
cargo-0.49.0/src/bin/cargo/commands/init.rs:1:5: usage of wildcard import
cargo-0.49.0/src/bin/cargo/commands/install.rs:1:5: usage of wildcard import
cargo-0.49.0/src/bin/cargo/commands/install.rs:97:16: use Option::map_or instead of an if let/else
cargo-0.49.0/src/bin/cargo/commands/locate_project.rs:1:5: usage of wildcard import
cargo-0.49.0/src/bin/cargo/commands/login.rs:1:5: usage of wildcard import
cargo-0.49.0/src/bin/cargo/commands/metadata.rs:1:5: usage of wildcard import
cargo-0.49.0/src/bin/cargo/commands/mod.rs:1:5: usage of wildcard import
cargo-0.49.0/src/bin/cargo/commands/new.rs:1:5: usage of wildcard import
cargo-0.49.0/src/bin/cargo/commands/new.rs:20:24: use Option::map_or instead of an if let/else
cargo-0.49.0/src/bin/cargo/commands/owner.rs:1:5: usage of wildcard import
cargo-0.49.0/src/bin/cargo/commands/owner.rs:38:43: redundant closure found
cargo-0.49.0/src/bin/cargo/commands/owner.rs:39:43: redundant closure found
cargo-0.49.0/src/bin/cargo/commands/owner.rs:40:43: redundant closure found
cargo-0.49.0/src/bin/cargo/commands/owner.rs:43:30: redundant closure found
cargo-0.49.0/src/bin/cargo/commands/owner.rs:46:30: redundant closure found
cargo-0.49.0/src/bin/cargo/commands/package.rs:1:5: usage of wildcard import
cargo-0.49.0/src/bin/cargo/commands/pkgid.rs:1:5: usage of wildcard import
cargo-0.49.0/src/bin/cargo/commands/publish.rs:1:5: usage of wildcard import
cargo-0.49.0/src/bin/cargo/commands/publish.rs:40:47: redundant closure found
cargo-0.49.0/src/bin/cargo/commands/read_manifest.rs:1:5: usage of wildcard import
cargo-0.49.0/src/bin/cargo/commands/run.rs:1:5: usage of wildcard import
cargo-0.49.0/src/bin/cargo/commands/rustc.rs:1:5: usage of wildcard import
cargo-0.49.0/src/bin/cargo/commands/rustdoc.rs:3:5: usage of wildcard import
cargo-0.49.0/src/bin/cargo/commands/search.rs:1:5: usage of wildcard import
cargo-0.49.0/src/bin/cargo/commands/test.rs:127:54: redundant closure found
cargo-0.49.0/src/bin/cargo/commands/test.rs:1:5: usage of wildcard import
cargo-0.49.0/src/bin/cargo/commands/tree.rs:149:49: redundant closure found
cargo-0.49.0/src/bin/cargo/commands/tree.rs:2:5: usage of wildcard import
cargo-0.49.0/src/bin/cargo/commands/uninstall.rs:1:5: usage of wildcard import
cargo-0.49.0/src/bin/cargo/commands/update.rs:1:5: usage of wildcard import
cargo-0.49.0/src/bin/cargo/commands/vendor.rs:1:5: usage of wildcard import
cargo-0.49.0/src/bin/cargo/commands/vendor.rs:96:16: called `map(<f>).unwrap_or_else(<g>)` on an `Option` value. This can be done more directly by calling `map_or_else(<g>, <f>)` instead
cargo-0.49.0/src/bin/cargo/commands/verify_project.rs:1:5: usage of wildcard import
cargo-0.49.0/src/bin/cargo/commands/version.rs:2:5: usage of wildcard import
cargo-0.49.0/src/bin/cargo/commands/yank.rs:1:5: usage of wildcard import
cargo-0.49.0/src/bin/cargo/commands/yank.rs:32:36: redundant closure found
cargo-0.49.0/src/bin/cargo/commands/yank.rs:33:35: redundant closure found
cargo-0.49.0/src/bin/cargo/commands/yank.rs:34:36: redundant closure found
cargo-0.49.0/src/bin/cargo/commands/yank.rs:35:36: redundant closure found
cargo-0.49.0/src/bin/cargo/main.rs:100:17: wildcard match will miss any future added variants
cargo-0.49.0/src/bin/cargo/main.rs:118:41: redundant closure found
cargo-0.49.0/src/bin/cargo/main.rs:137:43: redundant closure found
cargo-0.49.0/src/bin/cargo/main.rs:148:19: you seem to be trying to use match for destructuring a single pattern. Consider using `if let`
cargo-0.49.0/src/bin/cargo/main.rs:174:57: redundant closure found
cargo-0.49.0/src/bin/cargo/main.rs:18:5: usage of wildcard import
cargo-0.49.0/src/bin/cargo/main.rs:72:22: redundant closure found
cargo-0.49.0/src/bin/cargo/main.rs:94:13: wildcard match will miss any future added variants
cargo-0.49.0/src/bin/cargo/main.rs:96:41: redundant closure found
cargo-0.49.0/src/bin/cargo/main.rs:98:60: redundant closure found
cargo-0.49.0/src/cargo/core/compiler/build_config.rs:155:13: usage of wildcard import for enum variants
cargo-0.49.0/src/cargo/core/compiler/build_config.rs:170:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/compiler/build_config.rs:175:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/compiler/build_config.rs:180:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/compiler/build_config.rs:186:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/compiler/build_config.rs:197:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/compiler/build_config.rs:205:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/compiler/build_config.rs:51:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/compiler/build_config.rs:69:48: casting `usize` to `u32` may truncate the value on targets with 64-bit wide pointers
cargo-0.49.0/src/cargo/core/compiler/build_config.rs:96:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/compiler/build_context/mod.rs:44:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/compiler/build_context/mod.rs:83:20: you should put `x86_64` between ticks in the documentation
cargo-0.49.0/src/cargo/core/compiler/build_context/target_info.rs:108:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/compiler/build_context/target_info.rs:121:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/compiler/build_context/target_info.rs:149:9: adding items after statements is confusing, since items exist from the start of the scope
cargo-0.49.0/src/cargo/core/compiler/build_context/target_info.rs:420:69: you should put `mode/target_kind` between ticks in the documentation
cargo-0.49.0/src/cargo/core/compiler/build_context/target_info.rs:423:19: you should put `CrateTypes` between ticks in the documentation
cargo-0.49.0/src/cargo/core/compiler/build_context/target_info.rs:424:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/compiler/build_context/target_info.rs:469:58: redundant closure found
cargo-0.49.0/src/cargo/core/compiler/build_context/target_info.rs:591:20: called `filter(..).map(..)` on an `Iterator`
cargo-0.49.0/src/cargo/core/compiler/build_context/target_info.rs:603:19: redundant closure found
cargo-0.49.0/src/cargo/core/compiler/build_context/target_info.rs:665:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/compiler/build_context/target_info.rs:82:31: you should put `FileType` between ticks in the documentation
cargo-0.49.0/src/cargo/core/compiler/build_context/target_info.rs:83:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/compiler/build_context/target_info.rs:84:9: you seem to be trying to use match for destructuring a single pattern. Consider using `if let`
cargo-0.49.0/src/cargo/core/compiler/build_context/target_info.rs:96:31: you should put `FileType` between ticks in the documentation
cargo-0.49.0/src/cargo/core/compiler/build_context/target_info.rs:98:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/compiler/build_plan.rs:4:9: you should put `BuildPlan` between ticks in the documentation
cargo-0.49.0/src/cargo/core/compiler/build_plan.rs:5:66: you should put `BuildPlan` between ticks in the documentation
cargo-0.49.0/src/cargo/core/compiler/compilation.rs:150:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/compiler/compilation.rs:169:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/compiler/compilation.rs:185:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/compiler/compilation.rs:193:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/compiler/compilation.rs:194:49: redundant closure found
cargo-0.49.0/src/cargo/core/compiler/compilation.rs:198:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/compiler/compilation.rs:314:16: you should put `rustc_tool` between ticks in the documentation
cargo-0.49.0/src/cargo/core/compiler/compilation.rs:91:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/compiler/compile_kind.rs:118:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/compiler/compile_kind.rs:147:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/compiler/compile_kind.rs:157:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/compiler/compile_kind.rs:29:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/compiler/compile_kind.rs:33:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/compiler/compile_kind.rs:49:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/compiler/context/compilation_files.rs:204:9: you seem to be trying to use match for destructuring a single pattern. Consider using `if let`
cargo-0.49.0/src/cargo/core/compiler/context/compilation_files.rs:277:22: you should put `OUT_DIR` between ticks in the documentation
cargo-0.49.0/src/cargo/core/compiler/context/compilation_files.rs:324:66: you should put `FileType` between ticks in the documentation
cargo-0.49.0/src/cargo/core/compiler/context/compilation_files.rs:393:37: this `match` has identical arm bodies
cargo-0.49.0/src/cargo/core/compiler/context/compilation_files.rs:426:71: redundant closure found
cargo-0.49.0/src/cargo/core/compiler/context/mod.rs:125:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/compiler/context/mod.rs:125:5: this function has too many lines (107/100)
cargo-0.49.0/src/cargo/core/compiler/context/mod.rs:270:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/compiler/context/mod.rs:286:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/compiler/context/mod.rs:308:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/compiler/context/mod.rs:340:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/compiler/context/mod.rs:349:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/compiler/context/mod.rs:354:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/compiler/context/mod.rs:358:21: you should put `RunCustomBuild` between ticks in the documentation
cargo-0.49.0/src/cargo/core/compiler/context/mod.rs:361:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/compiler/context/mod.rs:365:9: called `find(..).map(..)` on an `Iterator`
cargo-0.49.0/src/cargo/core/compiler/context/mod.rs:374:43: you should put `RunCustomBuild` between ticks in the documentation
cargo-0.49.0/src/cargo/core/compiler/context/mod.rs:378:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/compiler/context/mod.rs:383:41: you should put `RunCustomBuild` between ticks in the documentation
cargo-0.49.0/src/cargo/core/compiler/context/mod.rs:384:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/compiler/context/mod.rs:391:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/compiler/context/mod.rs:397:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/compiler/context/mod.rs:523:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/compiler/context/mod.rs:538:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/compiler/context/mod.rs:542:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/compiler/context/mod.rs:83:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/compiler/context/mod.rs:92:25: you seem to be trying to use match for destructuring a single pattern. Consider using `if let`
cargo-0.49.0/src/cargo/core/compiler/crate_type.rs:16:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/compiler/crate_type.rs:29:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/compiler/crate_type.rs:40:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/compiler/crate_type.rs:49:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/compiler/crate_type.rs:60:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/compiler/custom_build.rs:150:1: this function has too many lines (230/100)
cargo-0.49.0/src/cargo/core/compiler/custom_build.rs:154:29: called `find(..).map(..)` on an `Iterator`
cargo-0.49.0/src/cargo/core/compiler/custom_build.rs:823:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/compiler/fingerprint.rs:1021:51: redundant closure found
cargo-0.49.0/src/cargo/core/compiler/fingerprint.rs:1252:20: called `filter(..).map(..)` on an `Iterator`
cargo-0.49.0/src/cargo/core/compiler/fingerprint.rs:1278:19: called `filter(..).map(..)` on an `Iterator`
cargo-0.49.0/src/cargo/core/compiler/fingerprint.rs:1656:16: you seem to be trying to use match for destructuring a single pattern. Consider using `if let`
cargo-0.49.0/src/cargo/core/compiler/fingerprint.rs:1986:17: binding's name is too similar to existing binding
cargo-0.49.0/src/cargo/core/compiler/fingerprint.rs:2016:5: adding items after statements is confusing, since items exist from the start of the scope
cargo-0.49.0/src/cargo/core/compiler/fingerprint.rs:61:5: you should put `CompileMode` between ticks in the documentation
cargo-0.49.0/src/cargo/core/compiler/fingerprint.rs:63:12: you should put `CompileKind` between ticks in the documentation
cargo-0.49.0/src/cargo/core/compiler/fingerprint.rs:67:7: you should put `CARGO_DEFAULT_LIB_METADATA[^4` between ticks in the documentation
cargo-0.49.0/src/cargo/core/compiler/fingerprint.rs:68:5: you should put `package_id` between ticks in the documentation
cargo-0.49.0/src/cargo/core/compiler/fingerprint.rs:71:19: you should put `test/bench/for_host/edition` between ticks in the documentation
cargo-0.49.0/src/cargo/core/compiler/fingerprint.rs:755:52: this `match` has identical arm bodies
cargo-0.49.0/src/cargo/core/compiler/fingerprint.rs:77:5: you should put `is_std` between ticks in the documentation
cargo-0.49.0/src/cargo/core/compiler/fingerprint.rs:816:5: this function has too many lines (127/100)
cargo-0.49.0/src/cargo/core/compiler/fingerprint.rs:863:64: binding's name is too similar to existing binding
cargo-0.49.0/src/cargo/core/compiler/fingerprint.rs:875:33: binding's name is too similar to existing binding
cargo-0.49.0/src/cargo/core/compiler/fingerprint.rs:876:32: binding's name is too similar to existing binding
cargo-0.49.0/src/cargo/core/compiler/fingerprint.rs:896:30: binding's name is too similar to existing binding
cargo-0.49.0/src/cargo/core/compiler/fingerprint.rs:897:30: binding's name is too similar to existing binding
cargo-0.49.0/src/cargo/core/compiler/fingerprint.rs:991:37: you seem to be trying to use match for destructuring a single pattern. Consider using `if let`
cargo-0.49.0/src/cargo/core/compiler/job_queue.rs:12:5: you should put `src/librustc_jobserver/lib.rs` between ticks in the documentation
cargo-0.49.0/src/cargo/core/compiler/job_queue.rs:282:30: called `filter(..).map(..)` on an `Iterator`
cargo-0.49.0/src/cargo/core/compiler/job_queue.rs:329:13: adding items after statements is confusing, since items exist from the start of the scope
cargo-0.49.0/src/cargo/core/compiler/job_queue.rs:332:23: this argument is passed by value, but not consumed in the function body
cargo-0.49.0/src/cargo/core/compiler/job_queue.rs:34:53: you should put `NeedsToken` between ticks in the documentation
cargo-0.49.0/src/cargo/core/compiler/job_queue.rs:35:6: you should put `ReleaseToken` between ticks in the documentation
cargo-0.49.0/src/cargo/core/compiler/job_queue.rs:37:6: you should put `NeedsToken` between ticks in the documentation
cargo-0.49.0/src/cargo/core/compiler/job_queue.rs:40:56: you should put `NeedsToken` between ticks in the documentation
cargo-0.49.0/src/cargo/core/compiler/job_queue.rs:40:5: you should put `NeedsToken` between ticks in the documentation
cargo-0.49.0/src/cargo/core/compiler/job_queue.rs:43:6: you should put `ReleaseToken` between ticks in the documentation
cargo-0.49.0/src/cargo/core/features.rs:119:17: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/features.rs:229:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/features.rs:274:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/features.rs:278:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/features.rs:306:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/features.rs:338:1: more than 3 bools in a struct
cargo-0.49.0/src/cargo/core/features.rs:362:25: consider using `Option<T>` instead of `Option<Option<T>>` or a custom enum if you need to distinguish all 3 cases
cargo-0.49.0/src/cargo/core/features.rs:380:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/features.rs:401:9: adding items after statements is confusing, since items exist from the start of the scope
cargo-0.49.0/src/cargo/core/features.rs:409:9: adding items after statements is confusing, since items exist from the start of the scope
cargo-0.49.0/src/cargo/core/features.rs:412:45: redundant closure found
cargo-0.49.0/src/cargo/core/features.rs:416:9: adding items after statements is confusing, since items exist from the start of the scope
cargo-0.49.0/src/cargo/core/features.rs:419:45: redundant closure found
cargo-0.49.0/src/cargo/core/features.rs:424:9: adding items after statements is confusing, since items exist from the start of the scope
cargo-0.49.0/src/cargo/core/features.rs:431:9: adding items after statements is confusing, since items exist from the start of the scope
cargo-0.49.0/src/cargo/core/features.rs:477:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/features.rs:509:1: this function could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/features.rs:518:5: called `map(<f>).unwrap_or_else(<g>)` on an `Option` value. This can be done more directly by calling `map_or_else(<g>, <f>)` instead
cargo-0.49.0/src/cargo/core/features.rs:542:1: this function could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/features.rs:543:37: redundant closure found
cargo-0.49.0/src/cargo/core/features.rs:547:60: redundant closure found
cargo-0.49.0/src/cargo/core/features.rs:556:1: item name ends with its containing module's name
cargo-0.49.0/src/cargo/core/features.rs:563:1: item name ends with its containing module's name
cargo-0.49.0/src/cargo/core/manifest.rs:116:13: usage of wildcard import for enum variants
cargo-0.49.0/src/cargo/core/manifest.rs:118:58: redundant closure found
cargo-0.49.0/src/cargo/core/manifest.rs:130:13: usage of wildcard import for enum variants
cargo-0.49.0/src/cargo/core/manifest.rs:143:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:159:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:162:34: redundant closure found
cargo-0.49.0/src/cargo/core/manifest.rs:169:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:17:5: usage of wildcard import
cargo-0.49.0/src/cargo/core/manifest.rs:189:1: more than 3 bools in a struct
cargo-0.49.0/src/cargo/core/manifest.rs:215:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:222:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:22:1: item name ends with its containing module's name
cargo-0.49.0/src/cargo/core/manifest.rs:360:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:407:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:410:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:413:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:416:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:419:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:422:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:425:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:431:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:438:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:444:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:447:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:450:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:453:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:456:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:459:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:462:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:466:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:470:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:477:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:481:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:488:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/manifest.rs:512:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:516:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:520:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:524:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:528:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:538:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:557:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:561:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:565:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:569:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:577:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:581:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:588:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:617:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:632:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:648:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:659:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:66:1: item name ends with its containing module's name
cargo-0.49.0/src/cargo/core/manifest.rs:670:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:693:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:708:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:723:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:726:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:729:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:735:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:738:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:741:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:744:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:747:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:751:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:754:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:757:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:760:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:763:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:767:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:776:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:780:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:787:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:798:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:800:56: redundant closure found
cargo-0.49.0/src/cargo/core/manifest.rs:805:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:809:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:818:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:823:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:828:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:831:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:834:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:839:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:85:1: item name starts with its containing module's name
cargo-0.49.0/src/cargo/core/manifest.rs:888:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/manifest.rs:936:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/package.rs:1075:28: redundant closure found
cargo-0.49.0/src/cargo/core/package.rs:160:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/package.rs:170:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/package.rs:174:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/package.rs:182:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/package.rs:186:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/package.rs:190:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/package.rs:194:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/package.rs:198:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/package.rs:202:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/package.rs:206:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/package.rs:210:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/package.rs:217:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/package.rs:221:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/package.rs:222:35: redundant closure found
cargo-0.49.0/src/cargo/core/package.rs:226:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/package.rs:227:35: redundant closure found
cargo-0.49.0/src/cargo/core/package.rs:230:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/package.rs:239:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/package.rs:249:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/package.rs:287:1: item name starts with its containing module's name
cargo-0.49.0/src/cargo/core/package.rs:385:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/package.rs:421:5: explicit lifetimes given in parameter types where they could be elided (or replaced with `'_` if needed by type declaration)
cargo-0.49.0/src/cargo/core/profiles.rs:397:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/profiles.rs:405:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/profiles.rs:607:1: more than 3 bools in a struct
cargo-0.49.0/src/cargo/core/profiles.rs:909:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/profiles.rs:923:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/profiles.rs:934:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/profiles.rs:987:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/registry.rs:111:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/registry.rs:127:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/registry.rs:168:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/registry.rs:19:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/registry.rs:240:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/registry.rs:26:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/registry.rs:344:49: redundant closure found
cargo-0.49.0/src/cargo/core/registry.rs:369:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/registry.rs:424:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/registry.rs:49:1: item name ends with its containing module's name
cargo-0.49.0/src/cargo/core/registry.rs:520:17: you seem to be trying to use match for destructuring a single pattern. Consider using `if let`
cargo-0.49.0/src/cargo/core/registry.rs:763:53: redundant closure found
cargo-0.49.0/src/cargo/core/registry.rs:765:53: redundant closure found
cargo-0.49.0/src/cargo/core/registry.rs:807:14: redundant closure found
cargo-0.49.0/src/cargo/core/registry.rs:814:53: redundant closure found
cargo-0.49.0/src/cargo/core/resolver/conflict_cache.rs:197:29: redundant closure found
cargo-0.49.0/src/cargo/core/resolver/conflict_cache.rs:41:38: called `map(<f>).unwrap_or_else(<g>)` on an `Option` value. This can be done more directly by calling `map_or_else(<g>, <f>)` instead
cargo-0.49.0/src/cargo/core/resolver/context.rs:274:53: redundant closure found
cargo-0.49.0/src/cargo/core/resolver/context.rs:297:9: called `filter(..).map(..)` on an `Iterator`
cargo-0.49.0/src/cargo/core/resolver/context.rs:42:1: item name starts with its containing module's name
cargo-0.49.0/src/cargo/core/resolver/context.rs:74:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/resolver/encode.rs:156:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/resolver/encode.rs:156:5: this function has too many lines (164/100)
cargo-0.49.0/src/cargo/core/resolver/encode.rs:339:17: wildcard match will miss any future added variants
cargo-0.49.0/src/cargo/core/resolver/encode.rs:438:5: adding items after statements is confusing, since items exist from the start of the scope
cargo-0.49.0/src/cargo/core/resolver/encode.rs:449:5: adding items after statements is confusing, since items exist from the start of the scope
cargo-0.49.0/src/cargo/core/resolver/encode.rs:529:34: redundant closure found
cargo-0.49.0/src/cargo/core/resolver/encode.rs:602:59: redundant closure found
cargo-0.49.0/src/cargo/core/resolver/encode.rs:623:1: item name starts with its containing module's name
cargo-0.49.0/src/cargo/core/resolver/encode.rs:652:27: you seem to be trying to use match for destructuring a single pattern. Consider using `if let`
cargo-0.49.0/src/cargo/core/resolver/encode.rs:674:51: redundant closure found
cargo-0.49.0/src/cargo/core/resolver/errors.rs:103:22: redundant closure found
cargo-0.49.0/src/cargo/core/resolver/errors.rs:104:22: redundant closure found
cargo-0.49.0/src/cargo/core/resolver/errors.rs:70:1: this function has too many lines (207/100)
cargo-0.49.0/src/cargo/core/resolver/features.rs:104:1: item name starts with its containing module's name
cargo-0.49.0/src/cargo/core/resolver/features.rs:111:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/resolver/features.rs:162:56: redundant closure found
cargo-0.49.0/src/cargo/core/resolver/features.rs:179:1: item name ends with its containing module's name
cargo-0.49.0/src/cargo/core/resolver/features.rs:186:23: you should put `RequestedFeatures` between ticks in the documentation
cargo-0.49.0/src/cargo/core/resolver/features.rs:187:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/resolver/features.rs:199:23: you should put `RequestedFeatures` between ticks in the documentation
cargo-0.49.0/src/cargo/core/resolver/features.rs:200:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/resolver/features.rs:209:9: called `filter(..).map(..)` on an `Iterator`
cargo-0.49.0/src/cargo/core/resolver/features.rs:221:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/resolver/features.rs:231:21: you should put `pkg_id/is_build` between ticks in the documentation
cargo-0.49.0/src/cargo/core/resolver/features.rs:233:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/resolver/features.rs:247:58: redundant closure found
cargo-0.49.0/src/cargo/core/resolver/features.rs:278:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/resolver/features.rs:394:27: you should put `FeatureValue` between ticks in the documentation
cargo-0.49.0/src/cargo/core/resolver/features.rs:460:19: you seem to be trying to use match for destructuring a single pattern. Consider using `if let`
cargo-0.49.0/src/cargo/core/resolver/features.rs:480:24: you should put `FeatureValues` between ticks in the documentation
cargo-0.49.0/src/cargo/core/resolver/features.rs:496:24: you should put `FeatureValues` between ticks in the documentation
cargo-0.49.0/src/cargo/core/resolver/features.rs:561:28: called `filter(..).map(..)` on an `Iterator`
cargo-0.49.0/src/cargo/core/resolver/features.rs:58:1: item name ends with its containing module's name
cargo-0.49.0/src/cargo/core/resolver/features.rs:67:1: more than 3 bools in a struct
cargo-0.49.0/src/cargo/core/resolver/mod.rs:1017:5: adding items after statements is confusing, since items exist from the start of the scope
cargo-0.49.0/src/cargo/core/resolver/mod.rs:1045:57: redundant closure found
cargo-0.49.0/src/cargo/core/resolver/mod.rs:122:1: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/resolver/mod.rs:142:44: redundant closure found
cargo-0.49.0/src/cargo/core/resolver/mod.rs:180:1: this function has too many lines (225/100)
cargo-0.49.0/src/cargo/core/resolver/mod.rs:311:17: you seem to be trying to use match for destructuring a single pattern. Consider using `if let`
cargo-0.49.0/src/cargo/core/resolver/mod.rs:421:52: called `filter_map(..).next()` on an `Iterator`. This is more succinctly expressed by calling `.find_map(..)` instead.
cargo-0.49.0/src/cargo/core/resolver/mod.rs:437:33: called `filter(..).map(..)` on an `Iterator`
cargo-0.49.0/src/cargo/core/resolver/mod.rs:457:69: called `filter_map(..).next()` on an `Iterator`. This is more succinctly expressed by calling `.find_map(..)` instead.
cargo-0.49.0/src/cargo/core/resolver/mod.rs:470:37: binding's name is too similar to existing binding
cargo-0.49.0/src/cargo/core/resolver/mod.rs:480:37: called `filter(..).map(..)` on an `Iterator`
cargo-0.49.0/src/cargo/core/resolver/mod.rs:607:11: this argument is passed by value, but not consumed in the function body
cargo-0.49.0/src/cargo/core/resolver/mod.rs:631:21: you seem to be trying to use match for destructuring a single pattern. Consider using `if let`
cargo-0.49.0/src/cargo/core/resolver/resolve.rs:239:5: explicit lifetimes given in parameter types where they could be elided (or replaced with `'_` if needed by type declaration)
cargo-0.49.0/src/cargo/core/resolver/resolve.rs:255:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/resolver/resolve.rs:259:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/resolver/resolve.rs:263:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/resolver/resolve.rs:269:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/resolver/resolve.rs:273:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/resolver/resolve.rs:274:9: called `map(<f>).unwrap_or_else(<g>)` on an `Option` value. This can be done more directly by calling `map_or_else(<g>, <f>)` instead
cargo-0.49.0/src/cargo/core/resolver/resolve.rs:280:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/resolver/resolve.rs:284:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/resolver/resolve.rs:288:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/resolver/resolve.rs:292:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/resolver/resolve.rs:296:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/resolver/resolve.rs:300:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/resolver/resolve.rs:315:13: called `map(<f>).unwrap_or_else(<g>)` on an `Option` value. This can be done more directly by calling `map_or_else(<g>, <f>)` instead
cargo-0.49.0/src/cargo/core/resolver/resolve.rs:354:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/resolver/resolve.rs:362:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/resolver/resolve.rs:60:1: item name starts with its containing module's name
cargo-0.49.0/src/cargo/core/resolver/resolve.rs:76:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/resolver/resolve.rs:90:35: called `filter(..).map(..)` on an `Iterator`
cargo-0.49.0/src/cargo/core/resolver/types.rs:111:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/core/resolver/types.rs:121:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/resolver/types.rs:141:19: you should put `ResolveOpts` between ticks in the documentation
cargo-0.49.0/src/cargo/core/resolver/types.rs:142:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/resolver/types.rs:149:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/core/resolver/types.rs:181:9: called `map(<f>).unwrap_or(<a>)` on an `Option` value. This can be done more directly by calling `map_or(<a>, <f>)` instead
cargo-0.49.0/src/cargo/core/resolver/types.rs:187:5: explicit lifetimes given in parameter types where they could be elided (or replaced with `'_` if needed by type declaration)
cargo-0.49.0/src/cargo/core/resolver/types.rs:261:5: explicit lifetimes given in parameter types where they could be elided (or replaced with `'_` if needed by type declaration)
cargo-0.49.0/src/cargo/ops/cargo_compile.rs:128:32: called `filter(..).map(..)` on an `Iterator`
cargo-0.49.0/src/cargo/ops/cargo_compile.rs:173:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/ops/cargo_compile.rs:205:36: this `match` has identical arm bodies
cargo-0.49.0/src/cargo/ops/cargo_compile.rs:242:1: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/ops/cargo_compile.rs:249:1: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/ops/cargo_compile.rs:258:1: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/ops/cargo_compile.rs:275:1: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/ops/cargo_compile.rs:275:1: this function has too many lines (219/100)
cargo-0.49.0/src/cargo/ops/cargo_compile.rs:468:9: calling `std::collections::HashMap::default()` is more clear than this expression
cargo-0.49.0/src/cargo/ops/cargo_compile.rs:548:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/ops/cargo_compile.rs:556:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/ops/cargo_compile.rs:574:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/ops/cargo_compile.rs:583:21: you should put `CompileFilter` between ticks in the documentation
cargo-0.49.0/src/cargo/ops/cargo_compile.rs:584:5: more than 3 bools in function parameters
cargo-0.49.0/src/cargo/ops/cargo_compile.rs:584:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/ops/cargo_compile.rs:592:9: binding's name is too similar to existing binding
cargo-0.49.0/src/cargo/ops/cargo_compile.rs:593:9: binding's name is too similar to existing binding
cargo-0.49.0/src/cargo/ops/cargo_compile.rs:607:13: binding's name is too similar to existing binding
cargo-0.49.0/src/cargo/ops/cargo_compile.rs:612:21: you should put `CompileFilter` between ticks in the documentation
cargo-0.49.0/src/cargo/ops/cargo_compile.rs:613:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/ops/cargo_compile.rs:618:9: binding's name is too similar to existing binding
cargo-0.49.0/src/cargo/ops/cargo_compile.rs:641:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/ops/cargo_compile.rs:652:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/ops/cargo_compile.rs:655:50: this `match` has identical arm bodies
cargo-0.49.0/src/cargo/ops/cargo_compile.rs:673:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/ops/cargo_compile.rs:692:49: this `match` has identical arm bodies
cargo-0.49.0/src/cargo/ops/cargo_compile.rs:703:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/ops/cargo_compile.rs:729:1: this function has too many lines (205/100)
cargo-0.49.0/src/cargo/ops/cargo_compile.rs:82:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/ops/cargo_compile.rs:874:69: redundant closure found
cargo-0.49.0/src/cargo/ops/cargo_doc.rs:20:1: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/ops/cargo_fetch.rs:15:1: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/ops/cargo_fetch.rs:27:46: redundant closure found
cargo-0.49.0/src/cargo/ops/cargo_fetch.rs:36:20: called `filter(..).map(..)` on an `Iterator`
cargo-0.49.0/src/cargo/ops/cargo_generate_lockfile.rs:160:5: adding items after statements is confusing, since items exist from the start of the scope
cargo-0.49.0/src/cargo/ops/cargo_generate_lockfile.rs:175:5: adding items after statements is confusing, since items exist from the start of the scope
cargo-0.49.0/src/cargo/ops/cargo_generate_lockfile.rs:22:1: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/ops/cargo_generate_lockfile.rs:37:1: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/ops/cargo_generate_lockfile.rs:37:1: this function has too many lines (171/100)
cargo-0.49.0/src/cargo/ops/cargo_install.rs:13:5: usage of wildcard import
cargo-0.49.0/src/cargo/ops/cargo_install.rs:148:1: more than 3 bools in function parameters
cargo-0.49.0/src/cargo/ops/cargo_install.rs:148:1: this function has too many lines (316/100)
cargo-0.49.0/src/cargo/ops/cargo_install.rs:202:17: redundant closure found
cargo-0.49.0/src/cargo/ops/cargo_install.rs:312:64: redundant closure found
cargo-0.49.0/src/cargo/ops/cargo_install.rs:318:63: called `filter(..).map(..)` on an `Iterator`
cargo-0.49.0/src/cargo/ops/cargo_install.rs:32:13: non-binding `let` on a type that implements `Drop`
cargo-0.49.0/src/cargo/ops/cargo_install.rs:37:1: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/ops/cargo_install.rs:454:22: redundant closure found
cargo-0.49.0/src/cargo/ops/cargo_install.rs:483:5: adding items after statements is confusing, since items exist from the start of the scope
cargo-0.49.0/src/cargo/ops/cargo_install.rs:683:1: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/ops/cargo_new.rs:101:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/ops/cargo_new.rs:245:5: adding items after statements is confusing, since items exist from the start of the scope
cargo-0.49.0/src/cargo/ops/cargo_new.rs:251:5: adding items after statements is confusing, since items exist from the start of the scope
cargo-0.49.0/src/cargo/ops/cargo_new.rs:367:1: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/ops/cargo_new.rs:405:1: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/ops/cargo_new.rs:489:5: you should put `IgnoreList` between ticks in the documentation
cargo-0.49.0/src/cargo/ops/cargo_new.rs:525:47: you should put `IgnoreList` between ticks in the documentation
cargo-0.49.0/src/cargo/ops/cargo_new.rs:525:9: you should put `format_existing` between ticks in the documentation
cargo-0.49.0/src/cargo/ops/cargo_new.rs:572:34: this `match` has identical arm bodies
cargo-0.49.0/src/cargo/ops/cargo_new.rs:623:1: this function has too many lines (130/100)
cargo-0.49.0/src/cargo/ops/cargo_new.rs:781:5: called `filter_map(..).next()` on an `Iterator`. This is more succinctly expressed by calling `.find_map(..)` instead.
cargo-0.49.0/src/cargo/ops/cargo_new.rs:800:16: you seem to be trying to use match for destructuring a single pattern. Consider using `if let`
cargo-0.49.0/src/cargo/ops/cargo_output_metadata.rs:163:36: redundant closure found
cargo-0.49.0/src/cargo/ops/cargo_output_metadata.rs:27:1: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/ops/cargo_output_metadata.rs:45:45: redundant closure found
cargo-0.49.0/src/cargo/ops/cargo_package.rs:144:1: this function has too many lines (112/100)
cargo-0.49.0/src/cargo/ops/cargo_package.rs:207:13: you seem to be trying to use match for destructuring a single pattern. Consider using `if let`
cargo-0.49.0/src/cargo/ops/cargo_package.rs:25:1: more than 3 bools in a struct
cargo-0.49.0/src/cargo/ops/cargo_package.rs:307:54: redundant closure found
cargo-0.49.0/src/cargo/ops/cargo_package.rs:394:5: adding items after statements is confusing, since items exist from the start of the scope
cargo-0.49.0/src/cargo/ops/cargo_package.rs:418:21: called `filter(..).map(..)` on an `Iterator`
cargo-0.49.0/src/cargo/ops/cargo_package.rs:425:61: redundant closure found
cargo-0.49.0/src/cargo/ops/cargo_package.rs:459:5: adding items after statements is confusing, since items exist from the start of the scope
cargo-0.49.0/src/cargo/ops/cargo_package.rs:66:1: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/ops/cargo_package.rs:769:29: called `filter(..).map(..)` on an `Iterator`
cargo-0.49.0/src/cargo/ops/common_for_install_and_uninstall.rs:392:9: called `find(..).map(..)` on an `Iterator`
cargo-0.49.0/src/cargo/ops/common_for_install_and_uninstall.rs:505:8: called `map(<f>).unwrap_or_else(<g>)` on an `Option` value. This can be done more directly by calling `map_or_else(<g>, <f>)` instead
cargo-0.49.0/src/cargo/ops/common_for_install_and_uninstall.rs:525:10: this argument is passed by value, but not consumed in the function body
cargo-0.49.0/src/cargo/ops/common_for_install_and_uninstall.rs:542:27: redundant closure found
cargo-0.49.0/src/cargo/ops/common_for_install_and_uninstall.rs:542:5: you seem to be trying to use match for destructuring a single pattern. Consider using `if let`
cargo-0.49.0/src/cargo/ops/common_for_install_and_uninstall.rs:613:5: adding items after statements is confusing, since items exist from the start of the scope
cargo-0.49.0/src/cargo/ops/common_for_install_and_uninstall.rs:645:41: you should put `BTreeSet` between ticks in the documentation
cargo-0.49.0/src/cargo/ops/common_for_install_and_uninstall.rs:654:42: called `filter(..).map(..)` on an `Iterator`
cargo-0.49.0/src/cargo/ops/common_for_install_and_uninstall.rs:662:14: called `filter(..).map(..)` on an `Iterator`
cargo-0.49.0/src/cargo/ops/common_for_install_and_uninstall.rs:674:17: called `filter(..).map(..)` on an `Iterator`
cargo-0.49.0/src/cargo/ops/common_for_install_and_uninstall.rs:681:17: called `filter(..).map(..)` on an `Iterator`
cargo-0.49.0/src/cargo/ops/common_for_install_and_uninstall.rs:92:19: you should put `InstallTracker` between ticks in the documentation
cargo-0.49.0/src/cargo/ops/fix.rs:200:1: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/ops/fix.rs:200:1: item name starts with its containing module's name
cargo-0.49.0/src/cargo/ops/fix.rs:424:20: called `map(<f>).unwrap_or(<a>)` on an `Option` value. This can be done more directly by calling `map_or(<a>, <f>)` instead
cargo-0.49.0/src/cargo/ops/fix.rs:455:13: binding's name is too similar to existing binding
cargo-0.49.0/src/cargo/ops/fix.rs:506:17: binding's name is too similar to existing binding
cargo-0.49.0/src/cargo/sources/registry/index.rs:736:1: explicit lifetimes given in parameter types where they could be elided (or replaced with `'_` if needed by type declaration)
cargo-0.49.0/src/cargo/sources/registry/remote.rs:32:1: item name starts with its containing module's name
cargo-0.49.0/src/cargo/sources/registry/remote.rs:72:13: you seem to be trying to use match for destructuring a single pattern. Consider using `if let`
cargo-0.49.0/src/cargo/sources/replaced.rs:12:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/sources/replaced.rs:5:1: item name starts with its containing module's name
cargo-0.49.0/src/cargo/util/canonical_url.rs:19:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/util/canonical_url.rs:65:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/util/command_prelude.rs:218:1: this function could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/util/command_prelude.rs:222:1: this function could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/util/command_prelude.rs:234:1: this function could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/util/command_prelude.rs:249:1: this function could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/util/command_prelude.rs:264:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/util/command_prelude.rs:279:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/util/command_prelude.rs:298:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/util/command_prelude.rs:320:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/util/command_prelude.rs:328:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/util/cpu.rs:11:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/util/cpu.rs:22:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/util/cpu.rs:82:25: casting `u64` to `f64` causes a loss of precision (`u64` is 64 bits wide, but `f64`'s mantissa is only 52 bits wide)
cargo-0.49.0/src/cargo/util/cpu.rs:82:9: casting `u64` to `f64` causes a loss of precision (`u64` is 64 bits wide, but `f64`'s mantissa is only 52 bits wide)
cargo-0.49.0/src/cargo/util/dependency_queue.rs:109:27: redundant closure found
cargo-0.49.0/src/cargo/util/dependency_queue.rs:136:20: called `filter(..).map(..)` on an `Iterator`
cargo-0.49.0/src/cargo/util/dependency_queue.rs:151:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/util/dependency_queue.rs:156:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/util/dependency_queue.rs:46:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/util/dependency_queue.rs:91:9: adding items after statements is confusing, since items exist from the start of the scope
cargo-0.49.0/src/cargo/util/diagnostic_server.rs:218:1: item name ends with its containing module's name
cargo-0.49.0/src/cargo/util/diagnostic_server.rs:230:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/util/diagnostic_server.rs:242:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/util/diagnostic_server.rs:58:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/util/diagnostic_server.rs:96:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/util/diagnostic_server.rs:96:5: this function has too many lines (110/100)
cargo-0.49.0/src/cargo/util/diagnostic_server.rs:99:21: `msg` is being shadowed
cargo-0.49.0/src/cargo/util/errors.rs:101:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/util/errors.rs:143:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/util/errors.rs:150:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/util/errors.rs:15:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/util/errors.rs:237:5: variant name ends with the enum's name
cargo-0.49.0/src/cargo/util/errors.rs:245:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/util/errors.rs:321:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/util/errors.rs:328:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/util/errors.rs:356:1: this function could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/util/errors.rs:391:5: adding items after statements is confusing, since items exist from the start of the scope
cargo-0.49.0/src/cargo/util/errors.rs:392:13: usage of wildcard import
cargo-0.49.0/src/cargo/util/errors.rs:465:1: this function could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/util/process_builder.rs:106:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/util/process_builder.rs:111:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/util/process_builder.rs:122:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/util/process_builder.rs:132:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/util/process_builder.rs:152:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/util/process_builder.rs:185:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/util/process_builder.rs:190:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/util/process_builder.rs:218:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/util/process_builder.rs:307:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/util/process_builder.rs:343:39: this argument is passed by value, but not consumed in the function body
cargo-0.49.0/src/cargo/util/progress.rs:122:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/util/progress.rs:136:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/util/progress.rs:15:1: item name starts with its containing module's name
cargo-0.49.0/src/cargo/util/progress.rs:249:19: casting `usize` to `f64` causes a loss of precision on targets with 64-bit wide pointers (`usize` is 64 bits wide, but `f64`'s mantissa is only 52 bits wide)
cargo-0.49.0/src/cargo/util/progress.rs:249:34: casting `usize` to `f64` causes a loss of precision on targets with 64-bit wide pointers (`usize` is 64 bits wide, but `f64`'s mantissa is only 52 bits wide)
cargo-0.49.0/src/cargo/util/progress.rs:263:22: casting `usize` to `f64` causes a loss of precision on targets with 64-bit wide pointers (`usize` is 64 bits wide, but `f64`'s mantissa is only 52 bits wide)
cargo-0.49.0/src/cargo/util/progress.rs:264:22: casting `f64` to `usize` may lose the sign of the value
cargo-0.49.0/src/cargo/util/progress.rs:264:22: casting `f64` to `usize` may truncate the value
cargo-0.49.0/src/cargo/util/progress.rs:89:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/util/progress.rs:97:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/util/queue.rs:25:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/util/read2.rs:11:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/util/read2.rs:31:17: binding's name is too similar to existing binding
cargo-0.49.0/src/cargo/util/restricted_names.rs:13:1: this function could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/util/restricted_names.rs:26:1: this function could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/util/restricted_names.rs:35:1: this function could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/util/restricted_names.rs:45:1: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/util/restricted_names.rs:87:1: this function could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/util/restricted_names.rs:89:21: redundant closure found
cargo-0.49.0/src/cargo/util/restricted_names.rs:8:1: this function could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/util/rustc.rs:103:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/util/rustc.rs:114:5: you should put bare URLs between `<`/`>` or make a proper Markdown link
cargo-0.49.0/src/cargo/util/rustc.rs:115:5: you should put bare URLs between `<`/`>` or make a proper Markdown link
cargo-0.49.0/src/cargo/util/rustc.rs:162:17: adding items after statements is confusing, since items exist from the start of the scope
cargo-0.49.0/src/cargo/util/rustc.rs:39:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/util/rustc.rs:55:13: called `find(..).map(..)` on an `Iterator`
cargo-0.49.0/src/cargo/util/sha256.rs:10:5: this method could have a `#[must_use]` attribute
cargo-0.49.0/src/cargo/util/sha256.rs:20:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/util/sha256.rs:31:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/util/sha256.rs:40:24: integer type suffix should be separated by an underscore
cargo-0.49.0/src/cargo/util/to_semver.rs:5:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/util/toml/mod.rs:1005:5: docs for function returning `Result` missing `# Errors` section
cargo-0.49.0/src/cargo/util/toml/mod.rs:1005:5: this function has too many lines (282/100)
cargo-0.49.0/src/cargo/util/toml/mod.rs:1094:36: redundant closure found
cargo-0.49.0/src/cargo/util/toml/mod.rs:1121:13: adding items after statements is confusing, since items exist from the start of the scope
cargo-0.49.0/src/cargo/util/toml/mod.rs:1197:32: called `map(<f>).unwrap_or_else(<g>)` on an `Option` value. This can be done more directly by calling `map_or_else(<g>, <f>)` instead
cargo-0.49.0/src/cargo/util/toml/mod.rs:124:1: docs for function returning `Result` missing `# Errors` section
libc-0.2.81/build.rs:114:19: called `map(<f>).unwrap_or(<a>)` on an `Option` value. This can be done more directly by calling `map_or(<a>, <f>)` instead
libc-0.2.81/src/unix/linux_like/linux/mod.rs:2596:52: used binding `_dummy` which is prefixed with an underscore. A leading underscore signals that a binding will not be used.
libc-0.2.81/src/unix/linux_like/linux/mod.rs:2597:11: casting `i32` to `usize` may lose the sign of the value
libc-0.2.81/src/unix/linux_like/linux/mod.rs:2601:21: it is more concise to loop over references to containers instead of using explicit iteration methods
proc-macro2-1.0.24/src/fallback.rs:430:24: this argument (0 byte) is passed by reference, but would be more efficient if passed by value (limit: 8 byte)
proc-macro2-1.0.24/src/fallback.rs:437:23: this argument (0 byte) is passed by reference, but would be more efficient if passed by value (limit: 8 byte)
proc-macro2-1.0.24/src/fallback.rs:471:17: this argument (0 byte) is passed by reference, but would be more efficient if passed by value (limit: 8 byte)
proc-macro2-1.0.24/src/parse.rs:602:20: called `map(<f>).unwrap_or(<a>)` on an `Option` value. This can be done more directly by calling `map_or(<a>, <f>)` instead
proc-macro2-1.0.24/src/parse.rs:696:29: casting `u8` to `u64` may become silently lossy if you later change the type
proc-macro2-1.0.24/src/parse.rs:702:34: casting `u8` to `u64` may become silently lossy if you later change the type
proc-macro2-1.0.24/src/parse.rs:708:34: casting `u8` to `u64` may become silently lossy if you later change the type
proc-macro2-1.0.24/src/parse.rs:803:15: it is more concise to loop over references to containers instead of using explicit iteration methods
proc-macro2-1.0.24/src/parse.rs:808:15: it is more concise to loop over references to containers instead of using explicit iteration methods
proc-macro2-1.0.24/src/wrapper.rs:415:24: this argument (4 byte) is passed by reference, but would be more efficient if passed by value (limit: 8 byte)
proc-macro2-1.0.24/src/wrapper.rs:429:23: this argument (4 byte) is passed by reference, but would be more efficient if passed by value (limit: 8 byte)
proc-macro2-1.0.24/src/wrapper.rs:492:17: this argument (4 byte) is passed by reference, but would be more efficient if passed by value (limit: 8 byte)
rand-0.7.3/src/distributions/bernoulli.rs:103:20: casting `f64` to `u64` may lose the sign of the value
rand-0.7.3/src/distributions/bernoulli.rs:103:20: casting `f64` to `u64` may truncate the value
rand-0.7.3/src/distributions/bernoulli.rs:116:5: docs for function returning `Result` missing `# Errors` section
rand-0.7.3/src/distributions/bernoulli.rs:123:21: casting `f64` to `u64` may lose the sign of the value
rand-0.7.3/src/distributions/bernoulli.rs:123:21: casting `f64` to `u64` may truncate the value
rand-0.7.3/src/distributions/bernoulli.rs:63:26: casting `u64` to `f64` causes a loss of precision (`u64` is 64 bits wide, but `f64`'s mantissa is only 52 bits wide)
rand-0.7.3/src/distributions/bernoulli.rs:63:27: integer type suffix should be separated by an underscore
rand-0.7.3/src/distributions/bernoulli.rs:67:1: item name starts with its containing module's name
rand-0.7.3/src/distributions/bernoulli.rs:95:5: docs for function returning `Result` missing `# Errors` section
rand-0.7.3/src/distributions/binomial.rs:107:23: casting `i64` to `f64` causes a loss of precision (`i64` is 64 bits wide, but `f64`'s mantissa is only 52 bits wide)
rand-0.7.3/src/distributions/binomial.rs:112:44: casting `i64` to `f64` causes a loss of precision (`i64` is 64 bits wide, but `f64`'s mantissa is only 52 bits wide)
rand-0.7.3/src/distributions/binomial.rs:116:13: adding items after statements is confusing, since items exist from the start of the scope
rand-0.7.3/src/distributions/binomial.rs:175:47: casting `i64` to `f64` causes a loss of precision (`i64` is 64 bits wide, but `f64`'s mantissa is only 52 bits wide)
rand-0.7.3/src/distributions/binomial.rs:185:38: casting `i64` to `f64` causes a loss of precision (`i64` is 64 bits wide, but `f64`'s mantissa is only 52 bits wide)
rand-0.7.3/src/distributions/binomial.rs:194:38: casting `i64` to `f64` causes a loss of precision (`i64` is 64 bits wide, but `f64`'s mantissa is only 52 bits wide)
rand-0.7.3/src/distributions/binomial.rs:209:25: casting `i64` to `f64` causes a loss of precision (`i64` is 64 bits wide, but `f64`'s mantissa is only 52 bits wide)
rand-0.7.3/src/distributions/binomial.rs:221:26: casting `i64` to `f64` causes a loss of precision (`i64` is 64 bits wide, but `f64`'s mantissa is only 52 bits wide)
rand-0.7.3/src/distributions/binomial.rs:222:26: casting `i64` to `f64` causes a loss of precision (`i64` is 64 bits wide, but `f64`'s mantissa is only 52 bits wide)
rand-0.7.3/src/distributions/binomial.rs:223:25: casting `i64` to `f64` causes a loss of precision (`i64` is 64 bits wide, but `f64`'s mantissa is only 52 bits wide)
rand-0.7.3/src/distributions/binomial.rs:224:25: casting `i64` to `f64` causes a loss of precision (`i64` is 64 bits wide, but `f64`'s mantissa is only 52 bits wide)
rand-0.7.3/src/distributions/binomial.rs:226:17: adding items after statements is confusing, since items exist from the start of the scope
rand-0.7.3/src/distributions/binomial.rs:233:32: casting `i64` to `f64` causes a loss of precision (`i64` is 64 bits wide, but `f64`'s mantissa is only 52 bits wide)
rand-0.7.3/src/distributions/binomial.rs:234:27: casting `i64` to `f64` causes a loss of precision (`i64` is 64 bits wide, but `f64`'s mantissa is only 52 bits wide)
rand-0.7.3/src/distributions/binomial.rs:251:22: casting `i64` to `u64` may lose the sign of the value
rand-0.7.3/src/distributions/binomial.rs:35:5: this method could have a `#[must_use]` attribute
rand-0.7.3/src/distributions/binomial.rs:45:17: casting `i64` to `f64` causes a loss of precision (`i64` is 64 bits wide, but `f64`'s mantissa is only 52 bits wide)
rand-0.7.3/src/distributions/binomial.rs:46:5: casting `f64` to `i64` may truncate the value
rand-0.7.3/src/distributions/binomial.rs:50:5: this function has too many lines (143/100)
rand-0.7.3/src/distributions/binomial.rs:76:9: adding items after statements is confusing, since items exist from the start of the scope
rand-0.7.3/src/distributions/binomial.rs:78:12: casting `u64` to `f64` causes a loss of precision (`u64` is 64 bits wide, but `f64`'s mantissa is only 52 bits wide)
rand-0.7.3/src/distributions/binomial.rs:81:21: casting `u64` to `f64` causes a loss of precision (`u64` is 64 bits wide, but `f64`'s mantissa is only 52 bits wide)
rand-0.7.3/src/distributions/binomial.rs:82:32: casting `u64` to `i32` may truncate the value
rand-0.7.3/src/distributions/binomial.rs:88:26: casting `u64` to `f64` causes a loss of precision (`u64` is 64 bits wide, but `f64`'s mantissa is only 52 bits wide)
rand-0.7.3/src/distributions/binomial.rs:99:21: casting `u64` to `f64` causes a loss of precision (`u64` is 64 bits wide, but `f64`'s mantissa is only 52 bits wide)
rand-0.7.3/src/distributions/cauchy.rs:33:5: this method could have a `#[must_use]` attribute
rand-0.7.3/src/distributions/dirichlet.rs:52:5: this method could have a `#[must_use]` attribute
rand-0.7.3/src/distributions/dirichlet.rs:64:32: float type suffix should be separated by an underscore
rand-0.7.3/src/distributions/dirichlet.rs:65:23: float type suffix should be separated by an underscore
rand-0.7.3/src/distributions/exponential.rs:76:5: this method could have a `#[must_use]` attribute
rand-0.7.3/src/distributions/float.rs:73:1: item name ends with its containing module's name
rand-0.7.3/src/distributions/gamma.rs:13:5: usage of wildcard import for enum variants
rand-0.7.3/src/distributions/gamma.rs:14:5: usage of wildcard import for enum variants
rand-0.7.3/src/distributions/gamma.rs:189:5: this method could have a `#[must_use]` attribute
rand-0.7.3/src/distributions/gamma.rs:230:5: this method could have a `#[must_use]` attribute
rand-0.7.3/src/distributions/gamma.rs:259:5: this method could have a `#[must_use]` attribute
rand-0.7.3/src/distributions/gamma.rs:287:5: this method could have a `#[must_use]` attribute
rand-0.7.3/src/distributions/gamma.rs:90:5: this method could have a `#[must_use]` attribute
rand-0.7.3/src/distributions/integer.rs:23:9: casting `u32` to `u8` may truncate the value
rand-0.7.3/src/distributions/integer.rs:30:9: casting `u32` to `u16` may truncate the value
rand-0.7.3/src/distributions/integer.rs:69:9: casting `u64` to `usize` may truncate the value on targets with 32-bit wide pointers
rand-0.7.3/src/distributions/mod.rs:263:5: you have declared `#[inline(always)]` on `next`. This is usually a bad idea
rand-0.7.3/src/distributions/normal.rs:100:5: this method could have a `#[must_use]` attribute
rand-0.7.3/src/distributions/normal.rs:119:1: item name ends with its containing module's name
rand-0.7.3/src/distributions/normal.rs:131:5: this method could have a `#[must_use]` attribute
rand-0.7.3/src/distributions/normal.rs:31:1: item name ends with its containing module's name
rand-0.7.3/src/distributions/normal.rs:47:25: float type suffix should be separated by an underscore
rand-0.7.3/src/distributions/normal.rs:48:25: float type suffix should be separated by an underscore
rand-0.7.3/src/distributions/other.rs:89:9: casting `u32` to `i32` may wrap around the value
rand-0.7.3/src/distributions/pareto.rs:32:5: this method could have a `#[must_use]` attribute
rand-0.7.3/src/distributions/poisson.rs:35:5: this method could have a `#[must_use]` attribute
rand-0.7.3/src/distributions/poisson.rs:87:30: casting `f64` to `u64` may lose the sign of the value
rand-0.7.3/src/distributions/poisson.rs:87:30: casting `f64` to `u64` may truncate the value
rand-0.7.3/src/distributions/triangular.rs:32:5: this method could have a `#[must_use]` attribute
rand-0.7.3/src/distributions/uniform.rs:146:4: needless `fn main` in doctest
rand-0.7.3/src/distributions/uniform.rs:199:1: item name ends with its containing module's name
rand-0.7.3/src/distributions/uniform.rs:214:1: item name starts with its containing module's name
rand-0.7.3/src/distributions/uniform.rs:283:14: you should put `SampleUniform` between ticks in the documentation
rand-0.7.3/src/distributions/uniform.rs:283:46: you should put `SampleUniform` between ticks in the documentation
rand-0.7.3/src/distributions/uniform.rs:296:5: you have declared `#[inline(always)]` on `borrow`. This is usually a bad idea
rand-0.7.3/src/distributions/uniform.rs:304:5: you have declared `#[inline(always)]` on `borrow`. This is usually a bad idea
rand-0.7.3/src/distributions/uniform.rs:350:1: item name starts with its containing module's name
rand-0.7.3/src/distributions/uniform.rs:407:21: redundant field names in struct initialization
rand-0.7.3/src/distributions/uniform.rs:407:21: redundant field names in struct initialization
rand-0.7.3/src/distributions/uniform.rs:407:21: redundant field names in struct initialization
rand-0.7.3/src/distributions/uniform.rs:407:21: redundant field names in struct initialization
rand-0.7.3/src/distributions/uniform.rs:407:21: redundant field names in struct initialization
rand-0.7.3/src/distributions/uniform.rs:407:21: redundant field names in struct initialization
rand-0.7.3/src/distributions/uniform.rs:407:21: redundant field names in struct initialization
rand-0.7.3/src/distributions/uniform.rs:407:21: redundant field names in struct initialization
rand-0.7.3/src/distributions/uniform.rs:407:21: redundant field names in struct initialization
rand-0.7.3/src/distributions/uniform.rs:407:21: redundant field names in struct initialization
rand-0.7.3/src/distributions/uniform.rs:407:21: redundant field names in struct initialization
rand-0.7.3/src/distributions/uniform.rs:407:21: redundant field names in struct initialization
rand-0.7.3/src/distributions/uniform.rs:441:31: because of the numeric bounds on `::core::u16::MAX` prior to casting, this expression is always false
rand-0.7.3/src/distributions/uniform.rs:441:31: because of the numeric bounds on `::core::u16::MAX` prior to casting, this expression is always false
rand-0.7.3/src/distributions/uniform.rs:441:31: because of the numeric bounds on `::core::u16::MAX` prior to casting, this expression is always false
rand-0.7.3/src/distributions/uniform.rs:441:31: because of the numeric bounds on `::core::u16::MAX` prior to casting, this expression is always false
rand-0.7.3/src/distributions/uniform.rs:441:31: because of the numeric bounds on `::core::u16::MAX` prior to casting, this expression is always false
rand-0.7.3/src/distributions/uniform.rs:441:31: because of the numeric bounds on `::core::u16::MAX` prior to casting, this expression is always false
rand-0.7.3/src/distributions/uniform.rs:441:31: because of the numeric bounds on `::core::u16::MAX` prior to casting, this expression is always false
rand-0.7.3/src/distributions/uniform.rs:441:31: because of the numeric bounds on `::core::u16::MAX` prior to casting, this expression is always false
rand-0.7.3/src/distributions/uniform.rs:56:10: you should put `SampleBorrow` between ticks in the documentation
rand-0.7.3/src/distributions/uniform.rs:647:1: item name starts with its containing module's name
rand-0.7.3/src/distributions/uniform.rs:840:1: item name starts with its containing module's name
rand-0.7.3/src/distributions/uniform.rs:913:13: use Option::map_or_else instead of an if let/else
rand-0.7.3/src/distributions/uniform.rs:943:54: casting `u64` to `u32` may truncate the value
rand-0.7.3/src/distributions/unit_circle.rs:30:5: this method could have a `#[must_use]` attribute
rand-0.7.3/src/distributions/unit_sphere.rs:24:1: item name starts with its containing module's name
rand-0.7.3/src/distributions/unit_sphere.rs:29:5: this method could have a `#[must_use]` attribute
rand-0.7.3/src/distributions/utils.rs:247:15: methods called `is_*` usually take self by reference or no self; consider choosing a less ambiguous name
rand-0.7.3/src/distributions/utils.rs:248:20: methods called `is_*` usually take self by reference or no self; consider choosing a less ambiguous name
rand-0.7.3/src/distributions/utils.rs:249:18: methods called `is_*` usually take self by reference or no self; consider choosing a less ambiguous name
rand-0.7.3/src/distributions/utils.rs:254:5: you have declared `#[inline(always)]` on `lanes`. This is usually a bad idea
rand-0.7.3/src/distributions/utils.rs:258:5: you have declared `#[inline(always)]` on `splat`. This is usually a bad idea
rand-0.7.3/src/distributions/utils.rs:262:5: you have declared `#[inline(always)]` on `extract`. This is usually a bad idea
rand-0.7.3/src/distributions/utils.rs:267:5: you have declared `#[inline(always)]` on `replace`. This is usually a bad idea
rand-0.7.3/src/distributions/utils.rs:281:5: you have declared `#[inline(always)]` on `any`. This is usually a bad idea
rand-0.7.3/src/distributions/utils.rs:286:5: you have declared `#[inline(always)]` on `all`. This is usually a bad idea
rand-0.7.3/src/distributions/utils.rs:291:5: you have declared `#[inline(always)]` on `none`. This is usually a bad idea
rand-0.7.3/src/distributions/utils.rs:488:17: you should put `x_i` between ticks in the documentation
rand-0.7.3/src/distributions/utils.rs:489:50: you should put `x_i` between ticks in the documentation
rand-0.7.3/src/distributions/utils.rs:489:63: you should put `f(x_i` between ticks in the documentation
rand-0.7.3/src/distributions/utils.rs:490:40: you should put `f(x_i` between ticks in the documentation
rand-0.7.3/src/distributions/utils.rs:490:49: you should put `f(x_{i+1` between ticks in the documentation
rand-0.7.3/src/distributions/utils.rs:518:17: casting `u64` to `usize` may truncate the value on targets with 32-bit wide pointers
rand-0.7.3/src/distributions/weibull.rs:29:5: this method could have a `#[must_use]` attribute
rand-0.7.3/src/distributions/weighted/alias_method.rs:113:21: it is more concise to loop over references to containers instead of using explicit iteration methods
rand-0.7.3/src/distributions/weighted/alias_method.rs:125:9: adding items after statements is confusing, since items exist from the start of the scope
rand-0.7.3/src/distributions/weighted/alias_method.rs:131:9: adding items after statements is confusing, since items exist from the start of the scope
rand-0.7.3/src/distributions/weighted/alias_method.rs:180:36: casting `usize` to `u32` may truncate the value on targets with 64-bit wide pointers
rand-0.7.3/src/distributions/weighted/alias_method.rs:182:34: casting `usize` to `u32` may truncate the value on targets with 64-bit wide pointers
rand-0.7.3/src/distributions/weighted/alias_method.rs:259:28: using `clone` on type `distributions::uniform::Uniform<u32>` which implements the `Copy` trait
rand-0.7.3/src/distributions/weighted/alias_method.rs:296:9: you are using an explicit closure for copying elements
rand-0.7.3/src/distributions/weighted/alias_method.rs:321:9: you are using an explicit closure for copying elements
rand-0.7.3/src/distributions/weighted/alias_method.rs:78:5: docs for function returning `Result` missing `# Errors` section
rand-0.7.3/src/distributions/weighted/alias_method.rs:78:5: this function has too many lines (106/100)
rand-0.7.3/src/distributions/weighted/alias_method.rs:85:17: casting `usize` to `u32` may truncate the value on targets with 64-bit wide pointers
rand-0.7.3/src/distributions/weighted/alias_method.rs:87:31: called `map(<f>).unwrap_or(<a>)` on an `Option` value. This can be done more directly by calling `map_or(<a>, <f>)` instead
rand-0.7.3/src/distributions/weighted/mod.rs:100:5: docs for function returning `Result` missing `# Errors` section
rand-0.7.3/src/distributions/weighted/mod.rs:144:5: docs for function returning `Result` missing `# Errors` section
rand-0.7.3/src/distributions/weighted/mod.rs:169:16: unnecessary `>= y + 1` or `x - 1 >=`
rand-0.7.3/src/distributions/weighted/mod.rs:386:1: item name starts with its containing module's name
rand-0.7.3/src/distributions/weighted/mod.rs:85:1: item name starts with its containing module's name
rand-0.7.3/src/lib.rs:333:5: docs for function returning `Result` missing `# Errors` section
rand-0.7.3/src/lib.rs:404:14: methods called `to_*` usually take self by reference; consider choosing a less ambiguous name
rand-0.7.3/src/lib.rs:552:1: this function could have a `#[must_use]` attribute
rand-0.7.3/src/rngs/adapter/read.rs:47:1: item name starts with its containing module's name
rand-0.7.3/src/rngs/adapter/read.rs:89:1: item name starts with its containing module's name
rand-0.7.3/src/rngs/adapter/reseeding.rs:100:5: docs for function returning `Result` missing `# Errors` section
rand-0.7.3/src/rngs/adapter/reseeding.rs:112:5: you have declared `#[inline(always)]` on `next_u32`. This is usually a bad idea
rand-0.7.3/src/rngs/adapter/reseeding.rs:117:5: you have declared `#[inline(always)]` on `next_u64`. This is usually a bad idea
rand-0.7.3/src/rngs/adapter/reseeding.rs:198:13: casting `u64` to `i64` may wrap around the value
rand-0.7.3/src/rngs/adapter/reseeding.rs:231:9: casting `usize` to `isize` may wrap around the value
rand-0.7.3/src/rngs/adapter/reseeding.rs:27:28: you should put `ChaCha` between ticks in the documentation
rand-0.7.3/src/rngs/adapter/reseeding.rs:79:1: item name starts with its containing module's name
rand-0.7.3/src/rngs/entropy.rs:24:1: item name starts with its containing module's name
rand-0.7.3/src/rngs/entropy.rs:34:5: this method could have a `#[must_use]` attribute
rand-0.7.3/src/rngs/mock.rs:36:5: this method could have a `#[must_use]` attribute
rand-0.7.3/src/rngs/mock.rs:47:9: casting `u64` to `u32` may truncate the value
rand-0.7.3/src/rngs/mod.rs:61:74: you should put `ChaCha20` between ticks in the documentation
rand-0.7.3/src/rngs/std.rs:25:39: you should put `ChaCha` between ticks in the documentation
rand-0.7.3/src/rngs/std.rs:32:10: you should put `rand_chacha` between ticks in the documentation
rand-0.7.3/src/rngs/std.rs:36:1: item name starts with its containing module's name
rand-0.7.3/src/rngs/std.rs:39:5: you have declared `#[inline(always)]` on `next_u32`. This is usually a bad idea
rand-0.7.3/src/rngs/std.rs:44:5: you have declared `#[inline(always)]` on `next_u64`. This is usually a bad idea
rand-0.7.3/src/rngs/std.rs:49:5: you have declared `#[inline(always)]` on `fill_bytes`. This is usually a bad idea
rand-0.7.3/src/rngs/std.rs:54:5: you have declared `#[inline(always)]` on `try_fill_bytes`. This is usually a bad idea
rand-0.7.3/src/rngs/std.rs:63:5: you have declared `#[inline(always)]` on `from_seed`. This is usually a bad idea
rand-0.7.3/src/rngs/std.rs:68:5: you have declared `#[inline(always)]` on `from_rng`. This is usually a bad idea
rand-0.7.3/src/rngs/thread.rs:57:1: item name starts with its containing module's name
rand-0.7.3/src/rngs/thread.rs:80:1: item name starts with its containing module's name
rand-0.7.3/src/rngs/thread.rs:80:1: this function could have a `#[must_use]` attribute
rand-0.7.3/src/rngs/thread.rs:81:35: redundant closure found
rand-0.7.3/src/rngs/thread.rs:93:5: you have declared `#[inline(always)]` on `next_u32`. This is usually a bad idea
rand-0.7.3/src/rngs/thread.rs:98:5: you have declared `#[inline(always)]` on `next_u64`. This is usually a bad idea
rand-0.7.3/src/seq/index.rs:127:1: item name starts with its containing module's name
rand-0.7.3/src/seq/index.rs:139:13: usage of wildcard import for enum variants
rand-0.7.3/src/seq/index.rs:159:1: item name starts with its containing module's name
rand-0.7.3/src/seq/index.rs:171:13: usage of wildcard import for enum variants
rand-0.7.3/src/seq/index.rs:180:13: usage of wildcard import for enum variants
rand-0.7.3/src/seq/index.rs:223:18: casting `usize` to `u32` may truncate the value on targets with 64-bit wide pointers
rand-0.7.3/src/seq/index.rs:224:18: casting `usize` to `u32` may truncate the value on targets with 64-bit wide pointers
rand-0.7.3/src/seq/index.rs:233:25: casting `u32` to `f32` causes a loss of precision (`u32` is 32 bits wide, but `f32`'s mantissa is only 23 bits wide)
rand-0.7.3/src/seq/index.rs:236:27: casting `u32` to `f32` causes a loss of precision (`u32` is 32 bits wide, but `f32`'s mantissa is only 23 bits wide)
rand-0.7.3/src/seq/index.rs:244:12: casting `u32` to `f32` causes a loss of precision (`u32` is 32 bits wide, but `f32`'s mantissa is only 23 bits wide)
rand-0.7.3/src/seq/index.rs:244:37: casting `u32` to `f32` causes a loss of precision (`u32` is 32 bits wide, but `f32`'s mantissa is only 23 bits wide)
rand-0.7.3/src/seq/index.rs:29:1: item name starts with its containing module's name
rand-0.7.3/src/seq/index.rs:39:5: this method could have a `#[must_use]` attribute
rand-0.7.3/src/seq/index.rs:48:5: this method could have a `#[must_use]` attribute
rand-0.7.3/src/seq/index.rs:60:5: this method could have a `#[must_use]` attribute
rand-0.7.3/src/seq/index.rs:69:5: this method could have a `#[must_use]` attribute
rand-0.7.3/src/seq/index.rs:78:5: this method could have a `#[must_use]` attribute
rand-0.7.3/src/seq/index.rs:87:5: method `into_iter` can be confused for the standard trait method `std::iter::IntoIterator::into_iter`
rand-0.7.3/src/seq/index.rs:87:5: this method could have a `#[must_use]` attribute
rand-0.7.3/src/seq/index.rs:97:13: usage of wildcard import for enum variants
rand-0.7.3/src/seq/mod.rs:141:5: docs for function returning `Result` missing `# Errors` section
rand-0.7.3/src/seq/mod.rs:168:5: docs for function returning `Result` missing `# Errors` section
rand-0.7.3/src/seq/mod.rs:229:4: needless `fn main` in doctest
rand-0.7.3/src/seq/mod.rs:292:29: casting `usize` to `f64` causes a loss of precision on targets with 64-bit wide pointers (`usize` is 64 bits wide, but `f64`'s mantissa is only 52 bits wide)
rand-0.7.3/src/seq/mod.rs:410:23: calling `std::marker::PhantomData::default()` is more clear than this expression
rand-0.7.3/src/seq/mod.rs:45:4: needless `fn main` in doctest
rand-0.7.3/src/seq/mod.rs:527:26: casting `usize` to `u32` may truncate the value on targets with 64-bit wide pointers
regex-1.3.2/src/exec.rs:383:41: you have declared `#[inline(always)]` on `shortest_match_at`. This is usually a bad idea
regex-1.3.2/src/exec.rs:388:41: you have declared `#[inline(always)]` on `is_match_at`. This is usually a bad idea
regex-1.3.2/src/exec.rs:393:41: you have declared `#[inline(always)]` on `find_at`. This is usually a bad idea
regex-1.3.2/src/exec.rs:398:41: you have declared `#[inline(always)]` on `captures_read_at`. This is usually a bad idea
regex-1.3.2/src/exec.rs:425:41: you have declared `#[inline(always)]` on `shortest_match_at`. This is usually a bad idea
regex-1.3.2/src/exec.rs:44:1: item name starts with its containing module's name
regex-1.3.2/src/exec.rs:473:9: you should put `shortest_match(...).is_some` between ticks in the documentation
regex-1.3.2/src/exec.rs:474:41: you have declared `#[inline(always)]` on `is_match_at`. This is usually a bad idea
regex-1.3.2/src/exec.rs:524:41: you have declared `#[inline(always)]` on `find_at`. This is usually a bad idea
regex-1.3.2/src/exec.rs:52:1: item name starts with its containing module's name
regex-1.3.2/src/exec.rs:686:13: usage of wildcard import for enum variants
regex-1.3.2/src/exec.rs:727:13: usage of wildcard import for enum variants
regex-1.3.2/src/exec.rs:767:13: usage of wildcard import for enum variants
regex-1.3.2/src/exec.rs:783:41: you have declared `#[inline(always)]` on `shortest_dfa`. This is usually a bad idea
regex-1.3.2/src/exec.rs:791:41: you have declared `#[inline(always)]` on `shortest_dfa_reverse_suffix`. This is usually a bad idea
regex-1.3.2/src/exec.rs:823:13: usage of wildcard import for enum variants
regex-1.3.2/src/exec.rs:868:13: usage of wildcard import for enum variants
regex-1.3.2/src/exec.rs:897:31: you should put `shortest_nfa(...).is_some` between ticks in the documentation
regex-1.3.2/src/exec.rs:899:9: you should put `shortest_nfa` between ticks in the documentation
regex-1.3.2/src/exec.rs:905:14: you should put `match_nfa` between ticks in the documentation
regex-1.3.2/src/exec.rs:930:14: you should put `shortest_nfa` between ticks in the documentation
regex-1.3.2/src/exec.rs:981:14: you should put `find_nfa` between ticks in the documentation
regex-1.3.2/src/expand.rs:170:27: this argument (1 byte) is passed by reference, but would be more efficient if passed by value (limit: 8 byte)
regex-1.3.2/src/expand.rs:171:5: match expression looks like `matches!` macro
regex-1.3.2/src/expand.rs:22:13: calling `push_str()` using a single-character string literal
regex-1.3.2/src/expand.rs:27:23: you seem to be trying to use match for destructuring a single pattern. Consider using `if let`
regex-1.3.2/src/expand.rs:30:17: calling `push_str()` using a single-character string literal
regex-1.3.2/src/expand.rs:38:30: called `map(<f>).unwrap_or(<a>)` on an `Option` value. This can be done more directly by calling `map_or(<a>, <f>)` instead
regex-1.3.2/src/expand.rs:42:21: called `map(<f>).unwrap_or(<a>)` on an `Option` value. This can be done more directly by calling `map_or(<a>, <f>)` instead
regex-1.3.2/src/expand.rs:50:1: item name starts with its containing module's name
regex-1.3.2/src/expand.rs:69:23: you seem to be trying to use match for destructuring a single pattern. Consider using `if let`
regex-1.3.2/src/expand.rs:80:28: called `map(<f>).unwrap_or(<a>)` on an `Option` value. This can be done more directly by calling `map_or(<a>, <f>)` instead
regex-1.3.2/src/expand.rs:84:21: called `map(<f>).unwrap_or(<a>)` on an `Option` value. This can be done more directly by calling `map_or(<a>, <f>)` instead
regex-1.3.2/src/expand.rs:8:1: item name starts with its containing module's name
regex-1.3.2/src/input.rs:142:1: item name ends with its containing module's name
regex-1.3.2/src/input.rs:146:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/input.rs:15:1: item name starts with its containing module's name
regex-1.3.2/src/input.rs:165:31: redundant field names in struct initialization
regex-1.3.2/src/input.rs:178:13: usage of wildcard import for enum variants
regex-1.3.2/src/input.rs:228:1: item name ends with its containing module's name
regex-1.3.2/src/input.rs:236:21: redundant field names in struct initialization
regex-1.3.2/src/input.rs:236:33: redundant field names in struct initialization
regex-1.3.2/src/input.rs:24:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/input.rs:271:13: usage of wildcard import for enum variants
regex-1.3.2/src/input.rs:29:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/input.rs:362:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/input.rs:370:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/input.rs:371:42: redundant closure found
regex-1.3.2/src/input.rs:37:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/input.rs:388:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/input.rs:42:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/input.rs:47:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/input.rs:53:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/input.rs:58:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/input.rs:63:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/literal/imp.rs:101:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/literal/imp.rs:114:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/literal/imp.rs:127:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/literal/imp.rs:139:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/literal/imp.rs:144:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/literal/imp.rs:149:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/literal/imp.rs:154:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/literal/imp.rs:155:13: usage of wildcard import for enum variants
regex-1.3.2/src/literal/imp.rs:160:30: this `match` has identical arm bodies
regex-1.3.2/src/literal/imp.rs:167:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/literal/imp.rs:168:13: usage of wildcard import for enum variants
regex-1.3.2/src/literal/imp.rs:78:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/literal/imp.rs:84:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/literal/imp.rs:850:20: long literal lacking separators
regex-1.3.2/src/literal/imp.rs:85:13: usage of wildcard import for enum variants
regex-1.3.2/src/pikevm.rs:103:15: redundant field names in struct initialization
regex-1.3.2/src/pikevm.rs:103:52: redundant field names in struct initialization
regex-1.3.2/src/pikevm.rs:114:5: this function has too many arguments (8/7)
regex-1.3.2/src/pikevm.rs:117:13: binding's name is too similar to existing binding
regex-1.3.2/src/pikevm.rs:124:17: binding's name is too similar to existing binding
regex-1.3.2/src/pikevm.rs:220:9: you should put `thread_caps` between ticks in the documentation
regex-1.3.2/src/pikevm.rs:222:16: you should put `at_next` between ticks in the documentation
regex-1.3.2/src/pikevm.rs:223:9: you should put `at_next` between ticks in the documentation
regex-1.3.2/src/pikevm.rs:224:5: this function has too many arguments (8/7)
regex-1.3.2/src/pikevm.rs:234:13: usage of wildcard import for enum variants
regex-1.3.2/src/pikevm.rs:303:13: usage of wildcard import for enum variants
regex-1.3.2/src/pikevm.rs:331:29: this expression mutably borrows a mutable reference. Consider reborrowing
regex-1.3.2/src/pikevm.rs:88:5: this function has too many arguments (8/7)
regex-1.3.2/src/prog.rs:102:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/prog.rs:113:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/prog.rs:120:9: match expression looks like `matches!` macro
regex-1.3.2/src/prog.rs:128:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/prog.rs:134:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/prog.rs:141:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/prog.rs:147:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/prog.rs:164:41: you have declared `#[inline(always)]` on `deref`. This is usually a bad idea
regex-1.3.2/src/prog.rs:172:13: usage of wildcard import for enum variants
regex-1.3.2/src/prog.rs:18:1: more than 3 bools in a struct
regex-1.3.2/src/prog.rs:236:13: using `write!()` with a format string that ends in a single newline
regex-1.3.2/src/prog.rs:300:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/prog.rs:301:9: match expression looks like `matches!` macro
regex-1.3.2/src/prog.rs:382:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/prog.rs:409:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/prog.rs:80:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/prog.rs:80:5: you should consider adding a `Default` implementation for `prog::Program`
regex-1.3.2/src/re_builder.rs:267:17: docs for function returning `Result` missing `# Errors` section
regex-1.3.2/src/re_builder.rs:267:17: docs for function returning `Result` missing `# Errors` section
regex-1.3.2/src/re_builder.rs:4:1: more than 3 bools in a struct
regex-1.3.2/src/re_builder.rs:57:17: this method could have a `#[must_use]` attribute
regex-1.3.2/src/re_builder.rs:57:17: this method could have a `#[must_use]` attribute
regex-1.3.2/src/re_builder.rs:68:17: docs for function returning `Result` missing `# Errors` section
regex-1.3.2/src/re_builder.rs:68:17: docs for function returning `Result` missing `# Errors` section
regex-1.3.2/src/re_bytes.rs:1017:9: called `map(<f>).unwrap_or_else(<g>)` on an `Option` value. This can be done more directly by calling `map_or_else(<g>, <f>)` instead
regex-1.3.2/src/re_bytes.rs:1039:9: called `map(<f>).unwrap_or_else(<g>)` on an `Option` value. This can be done more directly by calling `map_or_else(<g>, <f>)` instead
regex-1.3.2/src/re_bytes.rs:1093:5: explicit lifetimes given in parameter types where they could be elided (or replaced with `'_` if needed by type declaration)
regex-1.3.2/src/re_bytes.rs:1118:5: explicit lifetimes given in parameter types where they could be elided (or replaced with `'_` if needed by type declaration)
regex-1.3.2/src/re_bytes.rs:1133:5: explicit lifetimes given in parameter types where they could be elided (or replaced with `'_` if needed by type declaration)
regex-1.3.2/src/re_bytes.rs:118:5: docs for function returning `Result` missing `# Errors` section
regex-1.3.2/src/re_bytes.rs:256:13: redundant field names in struct initialization
regex-1.3.2/src/re_bytes.rs:29:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/re_bytes.rs:35:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/re_bytes.rs:42:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/re_bytes.rs:48:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/re_bytes.rs:558:29: you should put `shortest_match` between ticks in the documentation
regex-1.3.2/src/re_bytes.rs:55:33: redundant field names in struct initialization
regex-1.3.2/src/re_bytes.rs:55:47: redundant field names in struct initialization
regex-1.3.2/src/re_bytes.rs:572:29: you should put `is_match` between ticks in the documentation
regex-1.3.2/src/re_bytes.rs:720:13: redundant field names in struct initialization
regex-1.3.2/src/re_bytes.rs:817:5: you should put `CaptureLocations` between ticks in the documentation
regex-1.3.2/src/re_bytes.rs:843:1: item `re_bytes::CaptureLocations` has a public `len` method but no corresponding `is_empty` method
regex-1.3.2/src/re_bytes.rs:849:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/re_bytes.rs:858:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/re_bytes.rs:869:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/re_bytes.rs:891:1: item `re_bytes::Captures<'t>` has a public `len` method but no corresponding `is_empty` method
regex-1.3.2/src/re_bytes.rs:911:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/re_bytes.rs:917:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/re_bytes.rs:926:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/re_bytes.rs:955:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/re_set.rs:179:13: redundant field names in struct initialization
regex-1.3.2/src/re_set.rs:179:13: redundant field names in struct initialization
regex-1.3.2/src/re_set.rs:251:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/re_set.rs:251:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/re_set.rs:263:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/re_set.rs:263:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/re_set.rs:268:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/re_set.rs:268:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/re_set.rs:277:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/re_set.rs:277:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/re_set.rs:94:5: docs for function returning `Result` missing `# Errors` section
regex-1.3.2/src/re_set.rs:94:5: docs for function returning `Result` missing `# Errors` section
regex-1.3.2/src/re_trait.rs:136:29: redundant field names in struct initialization
regex-1.3.2/src/re_unicode.rs:1019:9: called `map(<f>).unwrap_or_else(<g>)` on an `Option` value. This can be done more directly by calling `map_or_else(<g>, <f>)` instead
regex-1.3.2/src/re_unicode.rs:1041:9: called `map(<f>).unwrap_or_else(<g>)` on an `Option` value. This can be done more directly by calling `map_or_else(<g>, <f>)` instead
regex-1.3.2/src/re_unicode.rs:1088:13: redundant field names in struct initialization
regex-1.3.2/src/re_unicode.rs:1135:5: explicit lifetimes given in parameter types where they could be elided (or replaced with `'_` if needed by type declaration)
regex-1.3.2/src/re_unicode.rs:1160:5: explicit lifetimes given in parameter types where they could be elided (or replaced with `'_` if needed by type declaration)
regex-1.3.2/src/re_unicode.rs:174:5: docs for function returning `Result` missing `# Errors` section
regex-1.3.2/src/re_unicode.rs:21:1: this function could have a `#[must_use]` attribute
regex-1.3.2/src/re_unicode.rs:313:13: redundant field names in struct initialization
regex-1.3.2/src/re_unicode.rs:38:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/re_unicode.rs:44:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/re_unicode.rs:51:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/re_unicode.rs:57:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/re_unicode.rs:617:29: you should put `shortest_match` between ticks in the documentation
regex-1.3.2/src/re_unicode.rs:631:29: you should put `is_match` between ticks in the documentation
regex-1.3.2/src/re_unicode.rs:64:33: redundant field names in struct initialization
regex-1.3.2/src/re_unicode.rs:64:47: redundant field names in struct initialization
regex-1.3.2/src/re_unicode.rs:834:5: you should put `CaptureLocations` between ticks in the documentation
regex-1.3.2/src/re_unicode.rs:860:1: item `re_unicode::CaptureLocations` has a public `len` method but no corresponding `is_empty` method
regex-1.3.2/src/re_unicode.rs:866:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/re_unicode.rs:875:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/re_unicode.rs:886:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/re_unicode.rs:908:1: item `re_unicode::Captures<'t>` has a public `len` method but no corresponding `is_empty` method
regex-1.3.2/src/re_unicode.rs:928:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/re_unicode.rs:934:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/re_unicode.rs:943:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/re_unicode.rs:972:5: this method could have a `#[must_use]` attribute
regex-1.3.2/src/sparse.rs:10:37: you should put bare URLs between `<`/`>` or make a proper Markdown link
regex-1.3.2/src/sparse.rs:15:1: item name starts with its containing module's name
regex-1.3.2/src/utf8.rs:100:16: digits of hex or binary literal not grouped by four
regex-1.3.2/src/utf8.rs:103:16: digits of hex or binary literal not grouped by four
regex-1.3.2/src/utf8.rs:106:22: casting `u8` to `u32` may become silently lossy if you later change the type
regex-1.3.2/src/utf8.rs:107:19: casting `u8` to `u32` may become silently lossy if you later change the type
regex-1.3.2/src/utf8.rs:108:19: casting `u8` to `u32` may become silently lossy if you later change the type
regex-1.3.2/src/utf8.rs:109:19: casting `u8` to `u32` may become silently lossy if you later change the type
regex-1.3.2/src/utf8.rs:111:27: long literal lacking separators
regex-1.3.2/src/utf8.rs:121:1: item name ends with its containing module's name
regex-1.3.2/src/utf8.rs:143:24: digits of hex or binary literal not grouped by four
regex-1.3.2/src/utf8.rs:143:9: digits of hex or binary literal not grouped by four
regex-1.3.2/src/utf8.rs:23:1: item name ends with its containing module's name
regex-1.3.2/src/utf8.rs:30:20: digits of hex or binary literal not grouped by four
regex-1.3.2/src/utf8.rs:51:1: item name ends with its containing module's name
regex-1.3.2/src/utf8.rs:58:23: digits of hex or binary literal not grouped by four
regex-1.3.2/src/utf8.rs:58:9: digits of hex or binary literal not grouped by four
regex-1.3.2/src/utf8.rs:63:16: digits of hex or binary literal not grouped by four
regex-1.3.2/src/utf8.rs:66:22: casting `u8` to `u32` may become silently lossy if you later change the type
regex-1.3.2/src/utf8.rs:66:54: casting `u8` to `u32` may become silently lossy if you later change the type
regex-1.3.2/src/utf8.rs:77:16: digits of hex or binary literal not grouped by four
regex-1.3.2/src/utf8.rs:80:16: digits of hex or binary literal not grouped by four
regex-1.3.2/src/utf8.rs:83:22: casting `u8` to `u32` may become silently lossy if you later change the type
regex-1.3.2/src/utf8.rs:84:19: casting `u8` to `u32` may become silently lossy if you later change the type
regex-1.3.2/src/utf8.rs:85:19: casting `u8` to `u32` may become silently lossy if you later change the type
regex-1.3.2/src/utf8.rs:92:23: digits of hex or binary literal not grouped by four
regex-1.3.2/src/utf8.rs:92:9: digits of hex or binary literal not grouped by four
regex-1.3.2/src/utf8.rs:97:16: digits of hex or binary literal not grouped by four
ripgrep-12.1.1/build.rs:133:19: called `.as_ref().map(|x| &**x)` on an Option value. This can be done more directly by calling `githash.as_deref()` instead
ripgrep-12.1.1/build.rs:18:18: you seem to be trying to use match for destructuring a single pattern. Consider using `if let`
ripgrep-12.1.1/build.rs:225:14: redundant closure found
ripgrep-12.1.1/build.rs:92:19: called `.as_ref().map(|x| &**x)` on an Option value. This can be done more directly by calling `githash.as_deref()` instead
ripgrep-12.1.1/crates/core/app.rs:1408:5: adding items after statements is confusing, since items exist from the start of the scope
ripgrep-12.1.1/crates/core/app.rs:1408:5: adding items after statements is confusing, since items exist from the start of the scope
ripgrep-12.1.1/crates/core/app.rs:1409:5: adding items after statements is confusing, since items exist from the start of the scope
ripgrep-12.1.1/crates/core/app.rs:1409:5: adding items after statements is confusing, since items exist from the start of the scope
ripgrep-12.1.1/crates/core/app.rs:152:32: you should put `clap::Arg` between ticks in the documentation
ripgrep-12.1.1/crates/core/app.rs:152:32: you should put `clap::Arg` between ticks in the documentation
ripgrep-12.1.1/crates/core/app.rs:156:39: you should put `clap::Arg` between ticks in the documentation
ripgrep-12.1.1/crates/core/app.rs:156:39: you should put `clap::Arg` between ticks in the documentation
ripgrep-12.1.1/crates/core/app.rs:156:5: you should put `RGArg` between ticks in the documentation
ripgrep-12.1.1/crates/core/app.rs:156:5: you should put `RGArg` between ticks in the documentation
ripgrep-12.1.1/crates/core/app.rs:1668:5: adding items after statements is confusing, since items exist from the start of the scope
ripgrep-12.1.1/crates/core/app.rs:1668:5: adding items after statements is confusing, since items exist from the start of the scope
ripgrep-12.1.1/crates/core/app.rs:1669:5: adding items after statements is confusing, since items exist from the start of the scope
ripgrep-12.1.1/crates/core/app.rs:1669:5: adding items after statements is confusing, since items exist from the start of the scope
ripgrep-12.1.1/crates/core/app.rs:1821:5: adding items after statements is confusing, since items exist from the start of the scope
ripgrep-12.1.1/crates/core/app.rs:1821:5: adding items after statements is confusing, since items exist from the start of the scope
ripgrep-12.1.1/crates/core/app.rs:1822:5: adding items after statements is confusing, since items exist from the start of the scope
ripgrep-12.1.1/crates/core/app.rs:1822:5: adding items after statements is confusing, since items exist from the start of the scope
ripgrep-12.1.1/crates/core/app.rs:2999:5: adding items after statements is confusing, since items exist from the start of the scope
ripgrep-12.1.1/crates/core/app.rs:2999:5: adding items after statements is confusing, since items exist from the start of the scope
ripgrep-12.1.1/crates/core/app.rs:3000:5: adding items after statements is confusing, since items exist from the start of the scope
ripgrep-12.1.1/crates/core/app.rs:3000:5: adding items after statements is confusing, since items exist from the start of the scope
ripgrep-12.1.1/crates/core/app.rs:367:54: this `match` has identical arm bodies
ripgrep-12.1.1/crates/core/app.rs:367:54: this `match` has identical arm bodies
ripgrep-12.1.1/crates/core/app.rs:414:59: this `match` has identical arm bodies
ripgrep-12.1.1/crates/core/app.rs:414:59: this `match` has identical arm bodies
ripgrep-12.1.1/crates/core/app.rs:417:57: this `match` has identical arm bodies
ripgrep-12.1.1/crates/core/app.rs:417:57: this `match` has identical arm bodies
ripgrep-12.1.1/crates/core/app.rs:417:57: this `match` has identical arm bodies
ripgrep-12.1.1/crates/core/app.rs:417:57: this `match` has identical arm bodies
ripgrep-12.1.1/crates/core/app.rs:444:41: this `match` has identical arm bodies
ripgrep-12.1.1/crates/core/app.rs:444:41: this `match` has identical arm bodies
ripgrep-12.1.1/crates/core/app.rs:470:41: this `match` has identical arm bodies
ripgrep-12.1.1/crates/core/app.rs:470:41: this `match` has identical arm bodies
ripgrep-12.1.1/crates/core/app.rs:75:9: you should put `RIPGREP_BUILD_GIT_HASH` between ticks in the documentation
ripgrep-12.1.1/crates/core/app.rs:75:9: you should put `RIPGREP_BUILD_GIT_HASH` between ticks in the documentation
ripgrep-12.1.1/crates/core/args.rs:1438:21: you should put `OsStr` between ticks in the documentation
ripgrep-12.1.1/crates/core/args.rs:1520:44: redundant closure found
ripgrep-12.1.1/crates/core/args.rs:1524:5: this function's return value is unnecessarily wrapped by `Result`
ripgrep-12.1.1/crates/core/args.rs:1635:14: you should put `values_of_lossy` between ticks in the documentation
ripgrep-12.1.1/crates/core/args.rs:1693:41: redundant closure found
ripgrep-12.1.1/crates/core/args.rs:1770:17: casting `u64` to `usize` may truncate the value on targets with 32-bit wide pointers
ripgrep-12.1.1/crates/core/args.rs:287:13: binding's name is too similar to existing binding
ripgrep-12.1.1/crates/core/args.rs:33:1: this import is redundant
ripgrep-12.1.1/crates/core/args.rs:34:1: this import is redundant
ripgrep-12.1.1/crates/core/args.rs:35:1: this import is redundant
ripgrep-12.1.1/crates/core/args.rs:410:14: this argument (2 byte) is passed by reference, but would be more efficient if passed by value (limit: 8 byte)
ripgrep-12.1.1/crates/core/args.rs:475:18: this `match` has identical arm bodies
ripgrep-12.1.1/crates/core/args.rs:512:19: you should put `ArgMatches` between ticks in the documentation
ripgrep-12.1.1/crates/core/args.rs:549:16: methods called `to_*` usually take self by reference; consider choosing a less ambiguous name
ripgrep-12.1.1/crates/core/args.rs:76:18: this argument (1 byte) is passed by reference, but would be more efficient if passed by value (limit: 8 byte)
ripgrep-12.1.1/crates/core/args.rs:77:13: usage of wildcard import for enum variants
ripgrep-12.1.1/crates/core/args.rs:923:42: you should put `BinaryDetection::quit` between ticks in the documentation
ripgrep-12.1.1/crates/core/config.rs:13:1: this import is redundant
ripgrep-12.1.1/crates/core/config.rs:58:6: very complex type used. Consider factoring parts into `type` definitions
ripgrep-12.1.1/crates/core/config.rs:79:6: very complex type used. Consider factoring parts into `type` definitions
ripgrep-12.1.1/crates/core/logger.rs:11:30: you should put `max_level` between ticks in the documentation
ripgrep-12.1.1/crates/core/logger.rs:15:16: constants have by default a `'static` lifetime
ripgrep-12.1.1/crates/core/main.rs:55:19: this argument is passed by value, but not consumed in the function body
ripgrep-12.1.1/crates/core/main.rs:56:9: usage of wildcard import for enum variants
ripgrep-12.1.1/crates/core/messages.rs:46:1: item name ends with its containing module's name
ripgrep-12.1.1/crates/core/messages.rs:51:1: item name ends with its containing module's name
ripgrep-12.1.1/crates/core/messages.rs:62:1: item name ends with its containing module's name
ripgrep-12.1.1/crates/core/path_printer.rs:27:1: item name starts with its containing module's name
ripgrep-12.1.1/crates/core/search.rs:185:1: item name starts with its containing module's name
ripgrep-12.1.1/crates/core/search.rs:292:9: using `write!()` with a format string that ends in a single newline
ripgrep-12.1.1/crates/core/search.rs:311:1: item name starts with its containing module's name
ripgrep-12.1.1/crates/core/search.rs:377:12: this boolean expression can be simplified
ripgrep-12.1.1/crates/core/search.rs:423:13: usage of wildcard import for enum variants
ripgrep-12.1.1/crates/core/search.rs:447:13: usage of wildcard import for enum variants
ripgrep-12.1.1/crates/core/search.rs:472:24: you are using an explicit closure for cloning elements
ripgrep-12.1.1/crates/core/search.rs:472:41: redundant closure found
ripgrep-12.1.1/crates/core/search.rs:480:24: you are using an explicit closure for cloning elements
ripgrep-12.1.1/crates/core/search.rs:480:41: redundant closure found
ripgrep-12.1.1/crates/core/search.rs:49:1: item name starts with its containing module's name
ripgrep-12.1.1/crates/core/search.rs:509:24: you are using an explicit closure for cloning elements
ripgrep-12.1.1/crates/core/search.rs:509:41: redundant closure found
ripgrep-12.1.1/crates/core/search.rs:517:24: you are using an explicit closure for cloning elements
ripgrep-12.1.1/crates/core/search.rs:517:41: redundant closure found
ripgrep-12.1.1/crates/core/search.rs:533:36: casting `u32` to `f64` may become silently lossy if you later change the type
ripgrep-12.1.1/crates/core/search.rs:533:5: casting `u64` to `f64` causes a loss of precision (`u64` is 64 bits wide, but `f64`'s mantissa is only 52 bits wide)
ripgrep-12.1.1/crates/core/subject.rs:20:1: item name starts with its containing module's name
ripgrep-12.1.1/crates/core/subject.rs:4:1: this import is redundant
xsv-0.13.0/src/cmd/sample.rs:105:44: casting `u64` to `usize` may truncate the value on targets with 32-bit wide pointers
xsv-0.13.0/src/cmd/sample.rs:115:21: casting `u64` to `usize` may truncate the value on targets with 32-bit wide pointers
xsv-0.13.0/src/cmd/sample.rs:11:16: statics have by default a `'static` lifetime
xsv-0.13.0/src/cmd/sample.rs:51:9: binding's name is too similar to existing binding
xsv-0.13.0/src/cmd/sample.rs:58:19: you seem to be trying to use match for destructuring a single pattern. Consider using `if let`
xsv-0.13.0/src/cmd/sample.rs:69:9: wildcard match will miss any future added variants
xsv-0.13.0/src/cmd/sample.rs:75:16: it is more concise to loop over containers instead of using explicit iteration methods
xsv-0.13.0/src/cmd/sample.rs:91:42: casting `u64` to `usize` may truncate the value on targets with 32-bit wide pointers
xsv-0.13.0/src/cmd/sample.rs:92:43: casting `u64` to `usize` may truncate the value on targets with 32-bit wide pointers
xsv-0.13.0/src/cmd/search.rs:51:9: binding's name is too similar to existing binding
xsv-0.13.0/src/cmd/search.rs:9:16: statics have by default a `'static` lifetime
xsv-0.13.0/src/cmd/select.rs:60:9: binding's name is too similar to existing binding
xsv-0.13.0/src/cmd/select.rs:8:16: statics have by default a `'static` lifetime
xsv-0.13.0/src/cmd/slice.rs:57:9: binding's name is too similar to existing binding
xsv-0.13.0/src/cmd/slice.rs:9:16: statics have by default a `'static` lifetime
xsv-0.13.0/src/cmd/sort.rs:11:16: statics have by default a `'static` lifetime
xsv-0.13.0/src/cmd/sort.rs:138:47: casting `i64` to `f64` causes a loss of precision (`i64` is 64 bits wide, but `f64`'s mantissa is only 52 bits wide)
xsv-0.13.0/src/cmd/sort.rs:139:51: casting `i64` to `f64` causes a loss of precision (`i64` is 64 bits wide, but `f64`'s mantissa is only 52 bits wide)
xsv-0.13.0/src/cmd/sort.rs:48:9: binding's name is too similar to existing binding
xsv-0.13.0/src/cmd/sort.rs:91:14: it is more concise to loop over containers instead of using explicit iteration methods
xsv-0.13.0/src/cmd/split.rs:131:36: trait objects without an explicit `dyn` are deprecated
xsv-0.13.0/src/cmd/split.rs:14:16: statics have by default a `'static` lifetime
xsv-0.13.0/src/cmd/split.rs:61:9: binding's name is too similar to existing binding
xsv-0.13.0/src/cmd/split.rs:94:5: this function's return value is unnecessarily wrapped by `Result`
xsv-0.13.0/src/cmd/split.rs:96:14: this argument is passed by value, but not consumed in the function body
xsv-0.13.0/src/cmd/split.rs:99:13: casting `u64` to `usize` may truncate the value on targets with 32-bit wide pointers
xsv-0.13.0/src/cmd/stats.rs:110:36: redundant closure found
xsv-0.13.0/src/cmd/stats.rs:127:14: this argument is passed by value, but not consumed in the function body
xsv-0.13.0/src/cmd/stats.rs:138:43: casting `u64` to `usize` may truncate the value on targets with 32-bit wide pointers
xsv-0.13.0/src/cmd/stats.rs:139:43: casting `u64` to `usize` may truncate the value on targets with 32-bit wide pointers
xsv-0.13.0/src/cmd/stats.rs:162:25: it is more concise to loop over containers instead of using explicit iteration methods
xsv-0.13.0/src/cmd/stats.rs:22:16: statics have by default a `'static` lifetime
xsv-0.13.0/src/cmd/stats.rs:231:1: more than 3 bools in a struct
xsv-0.13.0/src/cmd/stats.rs:262:35: calling `cmd::stats::TypedSum::default()` is more clear than this expression
xsv-0.13.0/src/cmd/stats.rs:263:40: calling `cmd::stats::TypedMinMax::default()` is more clear than this expression
xsv-0.13.0/src/cmd/stats.rs:264:39: calling `stats::OnlineStats::default()` is more clear than this expression
xsv-0.13.0/src/cmd/stats.rs:265:58: calling `stats::Unsorted::default()` is more clear than this expression
xsv-0.13.0/src/cmd/stats.rs:266:41: calling `stats::Unsorted::default()` is more clear than this expression
xsv-0.13.0/src/cmd/stats.rs:268:18: calling `cmd::stats::FieldType::default()` is more clear than this expression
xsv-0.13.0/src/cmd/stats.rs:269:13: redundant field names in struct initialization
xsv-0.13.0/src/cmd/stats.rs:270:13: redundant field names in struct initialization
xsv-0.13.0/src/cmd/stats.rs:271:13: redundant field names in struct initialization
xsv-0.13.0/src/cmd/stats.rs:272:13: redundant field names in struct initialization
xsv-0.13.0/src/cmd/stats.rs:273:13: redundant field names in struct initialization
xsv-0.13.0/src/cmd/stats.rs:274:13: redundant field names in struct initialization
xsv-0.13.0/src/cmd/stats.rs:283:9: called `map(f)` on an `Option` value where `f` is a closure that returns the unit type `()`
xsv-0.13.0/src/cmd/stats.rs:284:9: called `map(f)` on an `Option` value where `f` is a closure that returns the unit type `()`
xsv-0.13.0/src/cmd/stats.rs:285:9: called `map(f)` on an `Option` value where `f` is a closure that returns the unit type `()`
xsv-0.13.0/src/cmd/stats.rs:290:21: called `map(f)` on an `Option` value where `f` is a closure that returns the unit type `()`
xsv-0.13.0/src/cmd/stats.rs:293:25: this `match` has identical arm bodies
xsv-0.13.0/src/cmd/stats.rs:297:25: called `map(f)` on an `Option` value where `f` is a closure that returns the unit type `()`
xsv-0.13.0/src/cmd/stats.rs:301:21: called `map(f)` on an `Option` value where `f` is a closure that returns the unit type `()`
xsv-0.13.0/src/cmd/stats.rs:302:21: called `map(f)` on an `Option` value where `f` is a closure that returns the unit type `()`
xsv-0.13.0/src/cmd/stats.rs:308:18: methods called `to_*` usually take self by reference; consider choosing a less ambiguous name
xsv-0.13.0/src/cmd/stats.rs:318:9: you seem to be trying to use match for destructuring a single pattern. Consider using `if let`
xsv-0.13.0/src/cmd/stats.rs:322:45: redundant closure found
xsv-0.13.0/src/cmd/stats.rs:322:9: you seem to be trying to use match for destructuring a single pattern. Consider using `if let`
xsv-0.13.0/src/cmd/stats.rs:330:13: you seem to be trying to use match for destructuring a single pattern. Consider using `if let`
xsv-0.13.0/src/cmd/stats.rs:338:45: redundant closure found
xsv-0.13.0/src/cmd/stats.rs:402:16: redundant pattern matching, consider using `is_ok()`
xsv-0.13.0/src/cmd/stats.rs:403:16: redundant pattern matching, consider using `is_ok()`
xsv-0.13.0/src/cmd/stats.rs:407:18: this argument (1 byte) is passed by reference, but would be more efficient if passed by value (limit: 8 byte)
xsv-0.13.0/src/cmd/stats.rs:411:16: this argument (1 byte) is passed by reference, but would be more efficient if passed by value (limit: 8 byte)
xsv-0.13.0/src/cmd/stats.rs:427:56: this `match` has identical arm bodies
xsv-0.13.0/src/cmd/stats.rs:429:56: this `match` has identical arm bodies
xsv-0.13.0/src/cmd/stats.rs:430:60: this `match` has identical arm bodies
xsv-0.13.0/src/cmd/stats.rs:430:60: this `match` has identical arm bodies
xsv-0.13.0/src/cmd/stats.rs:454:5: you should put `TypedSum` between ticks in the documentation
xsv-0.13.0/src/cmd/stats.rs:473:43: casting `i64` to `f64` causes a loss of precision (`i64` is 64 bits wide, but `f64`'s mantissa is only 52 bits wide)
xsv-0.13.0/src/cmd/stats.rs:504:56: casting `i64` to `f64` causes a loss of precision (`i64` is 64 bits wide, but `f64`'s mantissa is only 52 bits wide)
xsv-0.13.0/src/cmd/stats.rs:505:51: casting `i64` to `f64` causes a loss of precision (`i64` is 64 bits wide, but `f64`'s mantissa is only 52 bits wide)
xsv-0.13.0/src/cmd/stats.rs:511:5: you should put `TypedMinMax` between ticks in the documentation
xsv-0.13.0/src/cmd/stats.rs:536:35: casting `f64` to `i64` may truncate the value
xsv-0.13.0/src/cmd/stats.rs:544:33: casting `i64` to `f64` causes a loss of precision (`i64` is 64 bits wide, but `f64`'s mantissa is only 52 bits wide)
xsv-0.13.0/src/cmd/stats.rs:592:22: calling `stats::MinMax::default()` is more clear than this expression
xsv-0.13.0/src/cmd/stats.rs:593:22: calling `stats::MinMax::default()` is more clear than this expression
xsv-0.13.0/src/cmd/stats.rs:594:23: calling `stats::MinMax::default()` is more clear than this expression
xsv-0.13.0/src/cmd/stats.rs:595:21: calling `stats::MinMax::default()` is more clear than this expression
xsv-0.13.0/src/cmd/stats.rs:71:1: more than 3 bools in a struct
xsv-0.13.0/src/cmd/stats.rs:86:9: binding's name is too similar to existing binding
xsv-0.13.0/src/cmd/table.rs:10:16: statics have by default a `'static` lifetime
xsv-0.13.0/src/cmd/table.rs:50:9: binding's name is too similar to existing binding
xsv-0.13.0/src/cmd/table.rs:54:9: binding's name is too similar to existing binding
xsv-0.13.0/src/config.rs:113:43: use of `unwrap_or` followed by a function call
xsv-0.13.0/src/config.rs:197:48: trait objects without an explicit `dyn` are deprecated
xsv-0.13.0/src/config.rs:202:48: trait objects without an explicit `dyn` are deprecated
xsv-0.13.0/src/config.rs:263:47: trait objects without an explicit `dyn` are deprecated
xsv-0.13.0/src/config.rs:293:47: trait objects without an explicit `dyn` are deprecated
xsv-0.13.0/src/config.rs:58:1: more than 3 bools in a struct
xsv-0.13.0/src/config.rs:90:13: redundant field names in struct initialization
xsv-0.13.0/src/index.rs:31:13: redundant field names in struct initialization
xsv-0.13.0/src/main.rs:164:49: redundant clone
xsv-0.13.0/src/main.rs:75:16: statics have by default a `'static` lifetime
xsv-0.13.0/src/select.rs:13:1: item name starts with its containing module's name
xsv-0.13.0/src/select.rs:154:5: this function's return value is unnecessarily wrapped by `Result`
xsv-0.13.0/src/select.rs:250:33: binding's name is too similar to existing binding
xsv-0.13.0/src/select.rs:250:43: binding's name is too similar to existing binding
xsv-0.13.0/src/select.rs:255:39: an inclusive range would be more readable
xsv-0.13.0/src/select.rs:280:20: length comparison to zero
xsv-0.13.0/src/select.rs:29:13: redundant field names in struct initialization
xsv-0.13.0/src/select.rs:360:62: this argument (8 byte) is passed by reference, but would be more efficient if passed by value (limit: 8 byte)
xsv-0.13.0/src/select.rs:360:9: this function's return value is unnecessarily wrapped by `Option`
xsv-0.13.0/src/select.rs:375:9: used sort instead of sort_unstable to sort primitive type `usize`
xsv-0.13.0/src/select.rs:379:18: it is more concise to loop over containers instead of using explicit iteration methods
xsv-0.13.0/src/select.rs:416:5: explicit lifetimes given in parameter types where they could be elided (or replaced with `'_` if needed by type declaration)
xsv-0.13.0/src/select.rs:419:9: this function's return value is unnecessarily wrapped by `Option`
xsv-0.13.0/src/select.rs:420:27: consider using `Option<T>` instead of `Option<Option<T>>` or a custom enum if you need to distinguish all 3 cases
xsv-0.13.0/src/select.rs:99:17: binding's name is too similar to existing binding
xsv-0.13.0/src/util.rs:150:5: you should put bare URLs between `<`/`>` or make a proper Markdown link
xsv-0.13.0/src/util.rs:190:48: trait objects without an explicit `dyn` are deprecated
xsv-0.13.0/src/util.rs:37:33: you are using an explicit closure for copying elements
xsv-0.13.0/src/util.rs:90:1: explicit lifetimes given in parameter types where they could be elided (or replaced with `'_` if needed by type declaration)
