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
Rename opcodes::All
to Opcode
#1955
Rename opcodes::All
to Opcode
#1955
Conversation
This all looks good. The Today I think It might be interesting to look at how Anyway concept ACK renaming |
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.
ACK ef9f049
Fix indentation of macro code and remove unnecessary line of whitespace.
This code comment is not commenting anything, remove it.
The opcode aliases are just that, aliases to opcodes so they can live in the `all` module along with the other opcodes.
The `opcodes::All` type can seemingly be re-named to `Opcode` with no loss of clarity - unless I'm missing something.
ef9f049
to
63d0fa0
Compare
Rebased, no other changes. |
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.
ACK 63d0fa0
I believe this can merge, it has one ack two weeks old now, I would argue that it counts as a "trivial API change that no one really cares about" - except @stevenroose who asked me to do this change anyways (out of band). |
I may be missing something about the
All
type but it seems it can be re-named toOpcode
with no loss of clarity.The first few patches do some other clean ups, the last patch is the meat and potatoes.