-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Require Output = ()
on WebSocketStream::on_upgrade
#636
Labels
A-axum
C-enhancement
Category: A PR with an enhancement
E-help-wanted
Call for participation: Help is requested to fix this issue.
Milestone
Comments
Makes sense 👍 |
davidpdrsn
added
A-axum
C-enhancement
Category: A PR with an enhancement
E-help-wanted
Call for participation: Help is requested to fix this issue.
labels
Dec 17, 2021
davidpdrsn
added a commit
that referenced
this issue
Dec 21, 2021
davidpdrsn
added a commit
that referenced
this issue
Dec 21, 2021
davidpdrsn
added a commit
that referenced
this issue
Dec 21, 2021
Fixed in #646 |
davidpdrsn
added a commit
that referenced
this issue
Dec 27, 2021
davidpdrsn
added a commit
that referenced
this issue
Jan 3, 2022
davidpdrsn
added a commit
that referenced
this issue
Jan 3, 2022
davidpdrsn
added a commit
that referenced
this issue
Jan 23, 2022
davidpdrsn
added a commit
that referenced
this issue
Jan 23, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-axum
C-enhancement
Category: A PR with an enhancement
E-help-wanted
Call for participation: Help is requested to fix this issue.
Feature Request
Motivation
By accepting a future with any return type, users can easily make a mistake if they for example give a future that outputs a
Result
, not realizing that theResult
will simply be ignored.Proposal
Change the bound on
WebSocketUpgrade::on_upgrade
toFut: Future<Output = ()>
in 0.5.The text was updated successfully, but these errors were encountered: