Cargo: Use futures-util and futures-channel to replace futures crate#30
Cargo: Use futures-util and futures-channel to replace futures crate#30cathay4t merged 1 commit intorust-netlink:mainfrom
futures-util and futures-channel to replace futures crate#30Conversation
…crate The `futures` crate contains more than we needs, this patch use `futures-channel` and `futures-channel` instead. Signed-off-by: Gris Ge <fge@redhat.com>
Summary of ChangesHello @cathay4t, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request refactors the project's asynchronous programming dependencies. By replacing the comprehensive Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request correctly replaces the futures crate with the more specific futures-util and futures-channel crates, which helps in reducing the dependency footprint. The changes across the source files are consistent with this goal. My main feedback is regarding the versions of the new dependencies in Cargo.toml, which are quite outdated; I've suggested updating them to more recent versions. Also, there's a small typo in the pull request description where futures-channel is mentioned twice instead of futures-util and futures-channel.
| futures-util = "0.3.11" | ||
| futures-channel = "0.3.11" |
There was a problem hiding this comment.
The versions specified for futures-util and futures-channel (0.3.11) are outdated. Using old versions of dependencies can introduce security vulnerabilities and bugs that have been fixed in newer releases. Please update to a more recent version, for example, 0.3.30.
| futures-util = "0.3.11" | |
| futures-channel = "0.3.11" | |
| futures-util = "0.3.30" | |
| futures-channel = "0.3.30" |
The
futurescrate contains more than we needs, this patch usefutures-channelandfutures-channelinstead.