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
As of now, signals don't have name, which means it is impossible, given a signal object, to know what signal it actually is, for example when logging a failure.
An optional name argument would be nice, even-though it would introduce some repetition
As of now, signals don't have name, which means it is impossible, given a signal object, to know what signal it actually is, for example when logging a failure.
An optional name argument would be nice, even-though it would introduce some repetition
To avoid the repetition, we could define signals as classes?
The text was updated successfully, but these errors were encountered: