-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
chore: bump revm to latest with placeholders for EOF #7765
Conversation
The database should contain only analyzed bytecode, so we do not have any checked ones. We can safely use unrechable! here. |
ec07eba
to
dfe323d
Compare
0a5b560
to
e2a73b4
Compare
3ba734b
to
aff06f3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
waiting for revm bump
aff06f3
to
aa98151
Compare
aa98151
to
3cb5064
Compare
len: buf.read_u64::<BigEndian>().unwrap() as usize, | ||
jump_map: JumpMap::from_slice(buf), | ||
}, | ||
1 => unreachable!("Junk data in database: checked Bytecode variant was removed"), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this safe to do ? Was this dead code even before?
Blocked on new revm release
I don't think this requires a breaking db change, but I also don't really know how to convert a checked bytecode from db
cc @rakita