-
Notifications
You must be signed in to change notification settings - Fork 190
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
Do not closeFd within sendFd #271
Conversation
We should use |
It is common to close a file descriptor after sending it, however it is not a required part of the work flow. There are uses for not closing a file descriptor. Closing the file descriptor is too high level of a decision.
34bdbc4
to
76d4802
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Merged. |
This seems like a huge change to slip into the package without so much as a minor version bump! It was added in the transition from 2.6.3.3 to 2.6.3.4 |
@glguy Sorry for your inconvenience. |
This probably needs to be a major version change, it changes the behavior of an existing function in a nonbackwards-compatible way. Code that uses this function will need to be modified to work after this change. The CPP macros can't even distinguish a change in the 4th component of a version number. |
You suggest:
Am I understanding correctly? |
It is common to close a file descriptor after sending it, however it is
not a required part of the work flow. There are uses for not closing a
file descriptor. Closing the file descriptor is too high level of a
decision.
Fix for #150