examples: Fix echo by Reintroducing Concurrency #1107
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In #808, I've added an
.await?to an instrumentedtokio::task::JoinHandlesince theInstrumentfuture now has a#[must_use]. However, this caused the echo example to no longer accept multiple netcat connections but was only reported in #1097. This PR resolves this bug by instrumenting the spawned future, not theJoinHandle.More broadly, I think the interaction between
tokio::task::JoinHandle(which does not have the#[must_use]annotation) and thetracing::Instrumentfuture (which does have the#[must_use]annotation) is confusing and introduces performance footguns in refactors that even advanced users missed in code review.Resolves #1097.