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

Change default lint level to warning and deny warnings in CI #397

Merged
merged 1 commit into from
Jul 9, 2020

Conversation

taiki-e
Copy link
Member

@taiki-e taiki-e commented Jun 7, 2020

If the API we are currently using becomes deprecated, deprecated warnings may prevent previously released versions from compiling. It can work around by --cap-lints, but it is not very good.

As we already applied -Dwarnings in CI, this PR only changes denied lints in code:

env:
RUSTFLAGS: -Dwarnings
RUST_BACKTRACE: 1

Also, seem to there is no way to pass -Dwarnings to the doc tests at the time, so this PR doesn't change the lint level of the doc tests. However, as #[doc(test(attr(deny(..)))] is enabled only when doc test is run, the above issue does not occur. See also rust-lang/futures-rs#1672 (comment) for this.

Related: tokio-rs/tokio#1083 (comment), rust-lang/futures-rs#1448 (comment)

Copy link
Member

@LucioFranco LucioFranco left a comment

Choose a reason for hiding this comment

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

seems fine to me, cc @carllerche

@seanmonstar seanmonstar merged commit 7daa7fe into master Jul 9, 2020
@seanmonstar seanmonstar deleted the warnings branch July 9, 2020 16:12
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.

3 participants