Closed<> followed by ConnectionError<> #671
Description
§10 contradicts itself in one paragraph:
No events will occur on a Connection after it is Closed; i.e., after a Closed<> event, an InitiateError<> or ConnectionError<> on that connection. To ensure this ordering, Closed<> will not occur on a Connection while other events on the Connection are still locally outstanding (i.e., known to the interface and waiting to be dealt with by the application). ConnectionError<> can occur after Closed<>, but the interface must gracefully handle all cases where the application ignores these errors.
It seems like Closed<> can and should be it: the stack should refuse any further interaction with userspace for this connection after that point.