You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#101 made sigaction unsafe because of soundness issues for thread-local storage. It's unfortunate that the really common use case of setting signals to default or ignore now requires unsafe.
The text was updated successfully, but these errors were encountered:
Could it be an idea to let sigaction stay as it is, and provide a sigaction_safe or named down the same line that prohibits the use of user-specified functions.
This could allow users to write sigaction_safe(Signal::SIGCHLD, SigHandler:SigIgn) and sigaction_safe(Signal::SIGCHLD, SigHandler:SigDfl)
Or would it be beneficial to not do this only at the sigaction function, but also at the creation of the SigAction struct?
#101 made
sigaction
unsafe because of soundness issues for thread-local storage. It's unfortunate that the really common use case of setting signals to default or ignore now requiresunsafe
.The text was updated successfully, but these errors were encountered: