Skip to content
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

Error handling within initializers #8793

Open
bradcray opened this issue Mar 12, 2018 · 0 comments
Open

Error handling within initializers #8793

bradcray opened this issue Mar 12, 2018 · 0 comments
Labels

Comments

@bradcray
Copy link
Member

As a Chapel Programmer, I would like the ability to throw errors from initializers and catch them when new objects are created because sometimes exceptional conditions can occur during object initialization and need to be handled within the program text without tearing the program down.

Acceptance criteria:
Initializers that throw errors can be written and their errors can be caught

@bradcray bradcray added the Epic label Mar 12, 2018
ronawho added a commit that referenced this issue Jun 11, 2018
Add halt wrappers for use in initializers and iterators

[reviewed by @mppf]

Error handling isn't supported for initializers or iterators today. These halt
wrappers are intended to mark such cases so that we can more easily
find/identify them in the future.

See #7134 and 
#8793 for more info
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant