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
We currently have a surprisingly big number of places where initiating an async operation derives in unpredictable and/or undefined behavior, . Since the introduction of any_connection, which does not expose the stream, all of these can be fixed to fail in a predictable way, without overhead. These are:
Initiating any async op while another op is outstanding.
Initiating any op after a previous op failed with a fatal error.
Initiating any op after a multi-function operation is initiated but not logically completed.
We can probably improve diagnostics when trying to use an unconnected connection.
A simple state machine in any_connection should suffice.
The text was updated successfully, but these errors were encountered:
We currently have a surprisingly big number of places where initiating an async operation derives in unpredictable and/or undefined behavior, . Since the introduction of any_connection, which does not expose the stream, all of these can be fixed to fail in a predictable way, without overhead. These are:
A simple state machine in any_connection should suffice.
The text was updated successfully, but these errors were encountered: