-
Notifications
You must be signed in to change notification settings - Fork 715
remove InterpreterResult as Result alias throughout and rename to VmExecutionResult
#6507
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
remove InterpreterResult as Result alias throughout and rename to VmExecutionResult
#6507
Conversation
Signed-off-by: Jacinta Ferrant <jacinta.ferrant@gmail.com>
Signed-off-by: Jacinta Ferrant <jacinta.ferrant@gmail.com>
I agree! I mean we are not in hurry and we could the less painfull way to remove this alias. |
… into chore/remove-interpreter-result-as-result
|
LGTM; happy to re-approve once merge conflicts are resolved |
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## develop #6507 +/- ##
===========================================
- Coverage 80.03% 79.77% -0.27%
===========================================
Files 565 565
Lines 346446 346528 +82
===========================================
- Hits 277282 276440 -842
- Misses 69164 70088 +924
... and 57 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
I am okay with removing InterpreterResult alias throughout the code base entirely but it will be quite a large change. Let me know your thoughts. (will also add some conflicts so might wait until the Error renames are done before doing the full replacement) If we do decide to keep InterpreterResult as VmExecutionResult, I will go throughout the codebase after to update all instances of Result<T, VmExecutionError> to use it as well but want feedback first.