-
-
Notifications
You must be signed in to change notification settings - Fork 393
Closed
Labels
Description
This isn't super urgent, but I want to make sure we revisit it before v1.0, so creating an issue that I can tag "potential API breaker".
Should we rename ResourceBusyError → BusyResourceError, for consistency with ClosedResourceError (and so the most meaningful part of the name come first)? Probably.
Should we consolidate BrokenStreamError, BrokenChannelError, etc., into a generic BrokenResourceError, like we did with ClosedResourceError and ResourceBusyError? Not sure. Maybe. The other ones it was mandatory because these exceptions passed between levels (e.g. socket -> stream). For the Broken family this isn't as likely, so we have the curse of options.
Reactions are currently unavailable