eval: add DetailedEvalErrors method to EvalTracer interface #6172
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
In #6170 and #6171 the EvalError details were removed to avoid unnecessary disassembly for error messages. This adds a method to the EvalTracer interface to allow certain use cases (unit tests, DeveloperAPI enabled) to request the additional detail.
Test Plan
Old versions of unit tests asserting specific opcodes in EvalError messages should work again in this PR.