Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Things I noticed while reviewing #49

Merged

Conversation

killercup
Copy link
Collaborator

⚠️ Targets #48's branch! Feel free to squash.

@killercup
Copy link
Collaborator Author

If nightly cargo was working, I'd've run clippy as well…

Copy link
Owner

@colin-kiegel colin-kiegel left a comment

Choose a reason for hiding this comment

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

Nice, thank you. I like all suggestions. I have only one remark regarding #[deny(warnings)]. If I understand the impact correctly, this would also fail a build, where derive_builder is only a dependency. I would instead suggest something like #[cfg(test, deny(warnings)], or #[cfg(dev_nightly, deny(warnings)].

Both should fail travis builds, without uneccessarily impairing a cargo build for a consumer of derive_builder. I think it's important to expect new depreciations in rustc at anytime and I wouldn't like that to stop derive_builder from compiling.

I'm on the train and I will merge when I'm at home. :-)

@killercup
Copy link
Collaborator Author

If I understand the impact correctly, this would also fail a build, where derive_builder is only a dependency.

Not if I understand RFC 1193 correctly: Cargo automatically passes --cap-lints allow, check cargo clean; cargo build --verbose.

Both should fail travis builds

You mean our travis builds? We'd need to have a compile step for each sub crate, then (because of cap-lints). Nice CI script, btw, using case is a great idea!

Speaking of CI, the nightly stuff is currently broken because of rust-lang/cargo#3819.

@colin-kiegel colin-kiegel merged commit 4514311 into colin-kiegel:feature/derive_builder_core Mar 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants