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

Cargo.toml: Remove deprecated executor-specific features #3001

Merged
merged 16 commits into from Oct 20, 2022

Conversation

thomaseizinger
Copy link
Contributor

Description

Links to any relevant issues

Open Questions

Change checklist

  • I have performed a self-review of my own code
  • I have made corresponding changes to the documentation
  • I have added tests that prove my fix is effective or that my feature works
  • A changelog entry has been made in the appropriate crates

We only want to emit the deprecation warning in case a user uses
the old features and _not_ the new ones. This assumes that a user
upgrades properly, i.e. adds the new `tokio` or `async-std` feature
AND removes the old `tcp-tokio` feature from the list.

We need to use this rather complex cfg expression because otherwise,
our CI won't pass. We run clippy with `--all-features`, thus just
detecting for presence of the `tcp-async-io` feature for example
will always flag our examples as using deprecated code.
Otherwise CI will not pass once #2963
actually checks it properly.
@mxinden
Copy link
Member

mxinden commented Oct 12, 2022

Thank you @thomaseizinger!

@thomaseizinger
Copy link
Contributor Author

This is blocked on the 0.49 release: #2931

Copy link
Member

@mxinden mxinden left a comment

Choose a reason for hiding this comment

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

@thomaseizinger thanks for preparing this. Can you bump the version in the root level Cargo.toml? Otherwise this looks good to me.

@thomaseizinger thomaseizinger marked this pull request as ready for review October 16, 2022 23:17
Copy link
Member

@mxinden mxinden left a comment

Choose a reason for hiding this comment

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

Looks good to me. Thanks for the follow-up.

@thomaseizinger
Copy link
Contributor Author

Interop tests fail for the same reasons as recently: We are bumping the version to 0.50 in this PR but testground doesn't yet know about that.

Proceeding with merge.

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.

None yet

2 participants