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

Improve exception_handling structure to allow for 'return' based exception handling. #653

Open
cafce25 opened this issue Nov 1, 2022 · 1 comment
Labels
Status: Discussion Needed For issues filed that need to be talked out first

Comments

@cafce25
Copy link
Contributor

cafce25 commented Nov 1, 2022

Expected Behavior

The exeception handling structure is useful for all kinds of exception handling.

Actual Behavior

Exception handling as it currently is implemeneted is only useful for 'try…catch' style exception handling.
If you try to implement the structures that use a 'return based' exeption handling like Rust or Haskell none of the available
concepts apply.

Steps to Reproduce the Problem

  1. Try to write up the exception_handling structure for one of the mentioned languages.
  2. None of the concepts apply.

Additional Info

Ideal would be to rewrite the current concepts to be compatible with both 'try…catch' and 'return' based exceptions if anyone can come up with a solution.
If that's not possible new concepts should be written accomodate for 'return' style exception handling.

@geekygirlsarah
Copy link
Member

I guess I might be unfamiliar with this style... do you have some good examples of what concepts this might include or examples in particular languages (since I see references to Rust and Haskell here)?

@geekygirlsarah geekygirlsarah added the Status: Discussion Needed For issues filed that need to be talked out first label Oct 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Discussion Needed For issues filed that need to be talked out first
Projects
None yet
Development

No branches or pull requests

2 participants