-
Notifications
You must be signed in to change notification settings - Fork 160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Notate abstract ops that can throw #371
Labels
editorial
Changes that do not affect how the standard is understood.
Comments
domenic
added
the
editorial
Changes that do not affect how the standard is understood.
label
Jul 2, 2015
Looks good |
This will be super helpful |
domenic
added a commit
that referenced
this issue
Aug 3, 2015
domenic
added a commit
that referenced
this issue
Aug 5, 2015
domenic
added a commit
that referenced
this issue
Aug 5, 2015
domenic
added a commit
that referenced
this issue
Aug 5, 2015
domenic
added a commit
that referenced
this issue
Aug 5, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#366 was a good first step in making the flow of potential exceptions clearer in the spec. We should also consider notating whether an abstract operation can throw or not so that callers know whether to use perform or to handle any abrupt completions.
Here's an approach:
The text was updated successfully, but these errors were encountered: