-
Notifications
You must be signed in to change notification settings - Fork 102
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
Expression processor: Results & Error Handling #2027
Conversation
Co-authored-by: chriseth <[email protected]>
Co-authored-by: chriseth <[email protected]>
…into expr_proc_results
Looks good! The only comment left is the updated test expectation. Is it just a temporary change? The untyped evaluator can be done in its own PR. |
Did you check if the escaping issue is a real issue (by running the commandline interface) or just a testing issue? |
Oh, yes, the three lines only occur when parsing the error during testing. When running the command line interface, the error is the same as the one that is created in the message |
No description provided.