-
Notifications
You must be signed in to change notification settings - Fork 734
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
Fix warnings about unexpected cfg(feature) values #2968
Conversation
The cfg for it was impossible to enable as of tokio-rs#441.
Previously, enabling this optional dependency did not do anything.
No need to use a custom cfg to run off-by-default tests.
It might be possible to make it work with tower_make instead, but that crate looks to be unmaintained (no longer present in the tower repo which is specified as the repository URL) so it should likely just be removed as a dependency.
@@ -71,33 +71,8 @@ where | |||
} | |||
} | |||
|
|||
#[cfg(feature = "tower-util")] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These could be migrated to tower_make
instead, see #2971
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, see the commit description for why I didn't do that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks!
@davidbarsky any reason this wasn't merged after approval? |
No reason other than "Phabricator taught me muscle memory that the PR author can land PRs/diffs after approval" 😅. Landing this. |
Motivation
CI is failing due to a new rustc lint. More about this lint in the recent blog post.
Solution
See individual commits. I chose different solutions for different parts of the codebase where warnings were emitted.