-
-
Notifications
You must be signed in to change notification settings - Fork 91
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
Async::Queue#signal
does not default value
to nil
#341
Comments
Apologies for this breaking change. Considering your investigation, do you think we should restore the default behaviour? If so, do you mind submitting a PR? |
I can make a PR, but it feels to me like the semantics of the For context our use of |
Confirmed, it looks like v2.3.0 which includes the changes in #187 fixed our issue, and we just haven't checked since then. So we can just remove the |
Awesome, let's keep this open and when I have time to review it in detail, I'll make a decision. |
I'm okay with following the same contract as |
#276 introduced a breaking change to the public interface of
Queue
. Prior to #276#signal
was inherited fromNotification
wherevalue
is defaulted tonil
if it is not provided.The new implementation of
Queue#signal
does not provide a default. Our implementation calls this method without an argument, and so now we are getting the following exception:The text was updated successfully, but these errors were encountered: