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

Upgrade Rust to version 1.76 #2148

Merged
merged 1 commit into from Mar 4, 2024
Merged

Upgrade Rust to version 1.76 #2148

merged 1 commit into from Mar 4, 2024

Conversation

luckysori
Copy link
Contributor

This upgrade highlighted the fact that we were using Node::connect in two different ways:

  • Caring about the returned value, a future that will be ready once the connection is dropped.
  • Not caring about the returned value.

Clippy was now complaining about us not always using the returned future. To fix this, I decided to split the API into two, so that the caller can be more explicit about what they want to do.

@luckysori luckysori self-assigned this Mar 4, 2024
This upgrade highlighted the fact that we were using `Node::connect`
in two different ways:

- Caring about the returned value, a future that will be ready once
the connection is dropped.
- Not caring about the returned value.

Clippy was now complaining about us not always using the returned
future. To fix this, I decided to split the API into two, so that the
caller can be more explicit about what they want to do.
Copy link
Contributor

@holzeis holzeis left a comment

Choose a reason for hiding this comment

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

Nice, thanks 👍

@luckysori luckysori added this pull request to the merge queue Mar 4, 2024
Merged via the queue into main with commit 44e329b Mar 4, 2024
20 checks passed
@luckysori luckysori deleted the chore/upgrade-rust-to-1-76 branch March 4, 2024 18:02
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