Skip to content
This repository has been archived by the owner on Aug 3, 2023. It is now read-only.

Nits: fix clippy warnings #427

Merged
merged 2 commits into from
Aug 13, 2019
Merged

Nits: fix clippy warnings #427

merged 2 commits into from
Aug 13, 2019

Conversation

xortive
Copy link
Contributor

@xortive xortive commented Aug 12, 2019

Cleaned up some clippy warnings that got past CI.

@@ -1,3 +1,4 @@
#![allow(dead_code)]
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

normally would be against this type of hammer, but I think this is an appropriate nail.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i'm confused is it a hammer or a nail 😉

Copy link
Contributor

@EverlastingBugstopper EverlastingBugstopper left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@@ -38,7 +38,7 @@ impl Package {

let package_json: String = fs::read_to_string(manifest_path.clone())?.parse()?;
let package: Package = serde_json::from_str(&package_json)
.expect(&format!("could not parse {:?}", manifest_path));
.unwrap_or_else(|_| panic!("could not parse {:?}", manifest_path));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Out of curiosity, why did expect cause these warnings?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants