Skip to content

Conversation

@Vlad-Shcherbina
Copy link
Contributor

Since the formatting string is "the answer to {} is {}.", question, answer,
the value of question should be "the ultimate question", not "the answer to...".

Since the formatting string is `"the answer to {} is {}.", question, answer`,
the value of `question` should be `"the ultimate question"`, not `"the answer to..."`.
@Vlad-Shcherbina Vlad-Shcherbina requested review from a team, davidbarsky and hawkw as code owners January 29, 2022 13:44
@hawkw hawkw enabled auto-merge (squash) February 1, 2022 19:07
@hawkw
Copy link
Member

hawkw commented Feb 1, 2022

Thanks, good catch!

@hawkw hawkw merged commit 1143858 into tokio-rs:master Feb 1, 2022
hawkw pushed a commit that referenced this pull request Feb 3, 2022
Since the formatting string is `"the answer to {} is {}.", question, answer`,
the value of `question` should be `"the ultimate question"`, not `"the answer to..."`.
hawkw pushed a commit that referenced this pull request Feb 3, 2022
Since the formatting string is `"the answer to {} is {}.", question, answer`,
the value of `question` should be `"the ultimate question"`, not `"the answer to..."`.
hawkw pushed a commit that referenced this pull request Feb 3, 2022
Since the formatting string is `"the answer to {} is {}.", question, answer`,
the value of `question` should be `"the ultimate question"`, not `"the answer to..."`.
hawkw pushed a commit that referenced this pull request Feb 3, 2022
Since the formatting string is `"the answer to {} is {}.", question, answer`,
the value of `question` should be `"the ultimate question"`, not `"the answer to..."`.
hawkw pushed a commit that referenced this pull request Feb 4, 2022
Since the formatting string is `"the answer to {} is {}.", question, answer`,
the value of `question` should be `"the ultimate question"`, not `"the answer to..."`.
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.

2 participants