-
Notifications
You must be signed in to change notification settings - Fork 10
Consider renaming ReceiverStoppedError to ReceiverClosedError #438
Copy link
Copy link
Open
Labels
part:coreAffects the core types (`Sender`, `Receiver`, exceptions, etc.)Affects the core types (`Sender`, `Receiver`, exceptions, etc.)priority:lowThis should be addressed only if there is nothing else on the tableThis should be addressed only if there is nothing else on the tabletype:enhancementNew feature or enhancement visitble to usersNew feature or enhancement visitble to userstype:tech-debtImproves the project without visible changes for usersImproves the project without visible changes for users
Milestone
Description
Activity
Metadata
Metadata
Assignees
Labels
part:coreAffects the core types (`Sender`, `Receiver`, exceptions, etc.)Affects the core types (`Sender`, `Receiver`, exceptions, etc.)priority:lowThis should be addressed only if there is nothing else on the tableThis should be addressed only if there is nothing else on the tabletype:enhancementNew feature or enhancement visitble to usersNew feature or enhancement visitble to userstype:tech-debtImproves the project without visible changes for usersImproves the project without visible changes for users
Type
Fields
Priority
None yet
Effort
None yet
What's needed?
Now that receivers have the
close()method, it feels a bit asymmetric to have an exception withStoppedinstead ofClosed.Proposed solution
ReceiverStoppedErrortoReceiverClosedErrornamedReceiverStoppedError(to keep backwards compatibility)