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

Distinguish between exception instances and exceptions that are actually raised during reduction #112

Closed
GoogleCodeExporter opened this issue Jun 21, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

We will introduce a ReductionException type which will wrap exceptions that are 
raised during reduction (i.e. reduceFully, uquote, text, raises, and raisesWith 
operators and extension methods). This will allow us to e.g. improve 
decompilation so that values of non-raised exceptions aren't printed with 
verbose stacktrace information. Note that this will be a slight breaking change 
in that the last expression returned from reduceAll will contain the 
ReductionException instead of the actual exception if one is thrown (use 
ReductionException.InnerException to get at the actual Exception).

Original issue reported on code.google.com by stephen....@gmail.com on 24 Mar 2015 at 2:34

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant