-
Notifications
You must be signed in to change notification settings - Fork 608
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
Add Channel#sendClose
#3279
Labels
Comments
I would like to work on this one :) |
tothpeti
added a commit
to tothpeti/fs2
that referenced
this issue
Aug 22, 2023
tothpeti
added a commit
to tothpeti/fs2
that referenced
this issue
Aug 22, 2023
tothpeti
added a commit
to tothpeti/fs2
that referenced
this issue
Aug 24, 2023
tothpeti
added a commit
to tothpeti/fs2
that referenced
this issue
Aug 24, 2023
tothpeti
added a commit
to tothpeti/fs2
that referenced
this issue
Aug 24, 2023
tothpeti
added a commit
to tothpeti/fs2
that referenced
this issue
Aug 24, 2023
tothpeti
added a commit
to tothpeti/fs2
that referenced
this issue
Sep 3, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
And also maybe
Channel#trySendClose
. Naming subject to bikeshed e.g.sendAndClose
?The idea is to be able to atomically
send
a final element to theChannel
and immediatelyclose
it. Withch.send(...) *> ch.close
there is a possibility that another concurrentsend
can sneak between.Motivation: in http4s/http4s#7196 we want to
close
theChannel
immediately upon sending a WebSocket CloseFrame.@tothpeti has kindly volunteered to work on this :)
The text was updated successfully, but these errors were encountered: