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
The iterator::backend::Handle has add_signal, but no remove_signal. This is a bit inconsistent and it turns out people would find it useful (see #63).
By implementing it on Handle, one would get the remove_signal for all the async structures's handles and the base iterator one. It still needs exposing on each of these types separately as a method wrapper (the signals.handle().remove_signal gets „propagated“ as the Handle type is the same one for all of them, but signals.remove_signal needs to actually be added).
The text was updated successfully, but these errors were encountered:
The
iterator::backend::Handle
hasadd_signal
, but noremove_signal
. This is a bit inconsistent and it turns out people would find it useful (see #63).By implementing it on
Handle
, one would get theremove_signal
for all the async structures's handles and the base iterator one. It still needs exposing on each of these types separately as a method wrapper (thesignals.handle().remove_signal
gets „propagated“ as the Handle type is the same one for all of them, butsignals.remove_signal
needs to actually be added).The text was updated successfully, but these errors were encountered: