We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Is your feature request related to a problem? Please describe. We can use
bytes4 selector = svm.createBytes4("selector"); vm.assume(bytes4(some_data) == selector);
pattern to print it in counterexamples. In the case of normal functions, it prints pretty functions names in counterexamples:
Counterexample: ... halmos_selector_bytes4_213bfa9_18 = withdraw
But if the function is ETH transferring (0x0) - it just prints
Counterexample: ... halmos_selector_bytes4_2b8420c_24 = 0x00000000
And I think such behavior may be enhanced
Describe the solution you'd like Maybe, print "transfer" instead of 0x00000000 ?
Additional context
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is your feature request related to a problem? Please describe.
We can use
pattern to print it in counterexamples.
In the case of normal functions, it prints pretty functions names in counterexamples:
But if the function is ETH transferring (0x0) - it just prints
And I think such behavior may be enhanced
Describe the solution you'd like
Maybe, print "transfer" instead of 0x00000000 ?
Additional context
The text was updated successfully, but these errors were encountered: