Skip to content

Conversation

@zerosnacks
Copy link
Member

@zerosnacks zerosnacks commented Dec 3, 2025

Motivation

We should be implementing log alongside log_full not either. This allows for vm.expectEmit to work against logs in cases where the interpreter is not available.

@zerosnacks zerosnacks marked this pull request as ready for review December 3, 2025 11:29
@zerosnacks zerosnacks self-assigned this Dec 3, 2025
@zerosnacks zerosnacks moved this to Ready For Review in Foundry Dec 3, 2025
Copy link
Contributor

@0xrusowsky 0xrusowsky left a comment

Choose a reason for hiding this comment

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

i think it makes sense

// Fail immediately
interpreter.bytecode.set_action(InterpreterAction::new_return(
InstructionResult::Revert,
Error::encode("log emitted but expected 0 times"),
Copy link
Contributor

Choose a reason for hiding this comment

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

optional nit: log emitted but not expected or smth like this?

Copy link
Member

Choose a reason for hiding this comment

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

msg shouldnt change here just keep it the same

@zerosnacks zerosnacks added this pull request to the merge queue Dec 4, 2025
Merged via the queue into master with commit aa40ad2 Dec 4, 2025
15 checks passed
@zerosnacks zerosnacks deleted the zerosnacks/log-support-revm branch December 4, 2025 15:50
@github-project-automation github-project-automation bot moved this from Ready For Review to Done in Foundry Dec 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

4 participants