feat: compose already existing signal handling #1768
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Nov 18, 2022
Signed-off-by: Joan Fontanals Martinez <[email protected]>
JoanFM
force-pushed
the
compose-signal-handling
branch
from
56dce4b
to
54470d9
Compare
|
Duplicated concern as #1600 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a draft PR to spark some discussion.
I would like UviServer to be able to not override
signal handlersalready installed, so I was thinking that perhaps overriding an already existing signal handler with a composition of the previous and the one needed byUviCorncould be a good idea.I know that we are accessing a private element that not every event loop implements and so on, but I would like to have your opinion about this problem and potential solutions before moving forward.