Skip to content

refactor(evm): add IntoInstructionResult bound to FoundryEvmFactory#14099

Merged
zerosnacks merged 1 commit intofoundry-rs:masterfrom
figtracer:feat/halt-reason-into-instruction-result
Apr 3, 2026
Merged

refactor(evm): add IntoInstructionResult bound to FoundryEvmFactory#14099
zerosnacks merged 1 commit intofoundry-rs:masterfrom
figtracer:feat/halt-reason-into-instruction-result

Conversation

@figtracer
Copy link
Copy Markdown
Collaborator

Motivation

Moves IntoInstructionResult from anvil to foundry-evm-core and adds HaltReason: IntoInstructionResult as a bound on FoundryEvmFactory. This enables generic code to convert network-specific halt reasons into InstructionResult without being pinned to Ethereum types.

…ryEvmFactory`

Move `IntoInstructionResult` from anvil to foundry-evm-core with impls
for `HaltReason`, `OpHaltReason`, and `TempoHaltReason`. Add
`HaltReason: IntoInstructionResult` bound to `FoundryEvmFactory` so
generic code can convert halt reasons to instruction results.
@figtracer figtracer marked this pull request as draft April 2, 2026 20:32
@figtracer figtracer marked this pull request as ready for review April 2, 2026 20:47
@figtracer figtracer changed the title refactor(evm): move IntoInstructionResult to core and bound FoundryEvmFactory refactor(evm): add IntoInstructionResult bound to FoundryEvmFactory Apr 2, 2026
@zerosnacks zerosnacks merged commit 07948c2 into foundry-rs:master Apr 3, 2026
15 checks passed
@github-project-automation github-project-automation Bot moved this to Done in Foundry Apr 3, 2026
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.

3 participants