-
Notifications
You must be signed in to change notification settings - Fork 494
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
Chore: Put the three doc strings about each op together #5708
Conversation
This PR should not affect any run-time behavior, nor any generated specs. It simply puts all of the documentation for an opcode together in one place, so it's slightly easier to add opcodes and find all of the documentation about an opcode in the source. An eventual further change might be to get the documentaion into the OpSpecs themselves, as there is still a little confusion there - immediates are _named_ in the OpSpec, but documented in doc.go.
6ee32b6
to
99c7327
Compare
Codecov Report
@@ Coverage Diff @@
## master #5708 +/- ##
==========================================
- Coverage 55.38% 54.69% -0.69%
==========================================
Files 466 466
Lines 65734 65734
==========================================
- Hits 36407 35955 -452
- Misses 26877 27293 +416
- Partials 2450 2486 +36
... and 51 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR essentially merge following 3 things:
opDocByName
opDocExtras
opcodeImmediateNotes
into one map of OpDesc
.
Removed the code path that allows pseudo-ops to execute non-existant opcodes. Changed tests to not test this path, and instead test that the pseudo-op annotation was properly placed on real opcode.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense
This PR should not affect any run-time behavior, nor any generated specs. It simply puts all of the documentation for an opcode together in one place, so it's slightly easier to add opcodes and find all of the documentation about an opcode in the source.
An eventual further change might be to get the documentaion into the OpSpecs themselves, as there is still a little confusion there - immediates are named in the OpSpec, but documented in doc.go.
The "test plan" here is really just that the generated specs are unchanged.