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/asm: change order of items in stringtokenTypes definition #24153

Merged
merged 1 commit into from
Dec 26, 2021

Conversation

zgfzgf
Copy link
Contributor

@zgfzgf zgfzgf commented Dec 24, 2021

No description provided.

@fjl
Copy link
Contributor

fjl commented Dec 25, 2021

Could you explain this change a bit more? It seems to be a purely aesthetic change with no performance impact whatsoever.

@zgfzgf
Copy link
Contributor Author

zgfzgf commented Dec 26, 2021

yes. a purely aesthetic change
but easier to view and understand code

@fjl
Copy link
Contributor

fjl commented Dec 26, 2021

Thanks, that clears it up. I was just curious because you said 'optimize' in PR title, but now it's clear you mean 'optimize readability'.

@fjl fjl modified the milestones: Backlog, 1.10.15 Dec 26, 2021
@fjl fjl merged commit 356bbe3 into ethereum:master Dec 26, 2021
@fjl fjl changed the title core/asm: optimize code core/asm: change order of items in stringtokenTypes definition Dec 26, 2021
sidhujag pushed a commit to syscoin/go-ethereum that referenced this pull request Dec 27, 2021
This orders the items in slice definition same as the enum values.
JacekGlen pushed a commit to JacekGlen/go-ethereum that referenced this pull request May 26, 2022
This orders the items in slice definition same as the enum values.
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.

2 participants