-
Notifications
You must be signed in to change notification settings - Fork 201
Add withFdSocket #352
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 withFdSocket #352
Conversation
`fdSocket` is fairly unsafe, because the socket may be finalized (and therefore closed) while the file descriptor is still being used. `withFdSocket` offers a safer way to use the file descriptor.
|
It looks like this accidentally includes commits from #351. Could you rebase those out? |
|
It's not an accident. The merge will otherwise be a bit annoying because of the import list changes. Let's resolve the other one first and then rebase this. |
|
@treeowl do you have any interest in continuing this PR, otherwise I'm going to close it as abandoned. |
|
Let's close this. |
|
Sorry, missed some notifications. I'd still be interested in rebasing to revive this. |
|
What's blocking this? |
|
Ugh. I'll get back to it this weekend, really. |
|
This is subsumed by #398 |
|
Closing this in favor of #398 |
fdSocketis fairly unsafe, because the socket may be finalized(and therefore closed) while the file descriptor is still being
used.
withFdSocketoffers a safer way to use the file descriptor.