Skip to content
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

core/vm: use proper JumpTable type #23967

Merged
merged 1 commit into from
Nov 25, 2021

Conversation

chfast
Copy link
Member

@chfast chfast commented Nov 24, 2021

No description provided.

Copy link
Contributor

@holiman holiman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM (aside from the fact that we have the parameter name being exactly identical to the type name -- which does not look good to me. However, I can't blame this PR for that)

@chfast
Copy link
Member Author

chfast commented Nov 25, 2021

It looks the jumpTable field can be private.

@chfast
Copy link
Member Author

chfast commented Nov 25, 2021

Or we can name the type: OperationTable or operationTable, and the field opTable or OpTable.

@karalabe karalabe added this to the 1.10.14 milestone Nov 25, 2021
@karalabe karalabe merged commit 4ebeca1 into ethereum:master Nov 25, 2021
@chfast chfast deleted the evm_jumptable_type branch November 25, 2021 12:23
sidhujag pushed a commit to syscoin/go-ethereum that referenced this pull request Nov 25, 2021
gzliudan pushed a commit to gzliudan/XDPoSChain that referenced this pull request Mar 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants