Skip to content

core/vm: fix typo callInexistant -> callInexistent in runtime_test.go #31958

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Caplost
Copy link

@Caplost Caplost commented Jun 4, 2025

Fix typo: callInexistant -> callInexistent in runtime_test.go

Summary

This PR fixes a spelling error in the variable name callInexistant which should be callInexistent (meaning "nonexistent").

Changes

  • File: core/vm/runtime/runtime_test.go
  • Change: Renamed variable callInexistant to callInexistent (lines 455 and 495)
  • Type: Spelling/typo fix
  • Impact: Code readability improvement, no functional changes

Details

The variable callInexistant was incorrectly spelled. The correct spelling is callInexistent, which properly conveys the meaning that it's calling a nonexistent contract address (0xff) for benchmarking purposes.

Before:

callInexistant := p.
    Call(nil, 0xff, 0, 0, 0, 0, 0).
    Op(vm.POP).Jump(lbl).Bytes()

benchmarkNonModifyingCode(100000000, callInexistant, "call-nonexist-100M", "", b)

After:

callInexistent := p.
    Call(nil, 0xff, 0, 0, 0, 0, 0).
    Op(vm.POP).Jump(lbl).Bytes()

benchmarkNonModifyingCode(100000000, callInexistent, "call-nonexist-100M", "", b)

Testing

  • No functional changes, only variable naming
  • Existing tests should continue to pass
  • No new tests required

Checklist

  • Code follows the project's coding standards
  • Changes are minimal and focused
  • No breaking changes
  • Documentation not needed (variable name change only)

This is a minor quality-of-life improvement that enhances code readability by fixing the spelling error.

@Caplost Caplost requested a review from rjl493456442 as a code owner June 4, 2025 06:58
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.

1 participant