-
Notifications
You must be signed in to change notification settings - Fork 857
[Doc] Cleanup Bus-Mapping, ExecutionSteps, and ExecutionTrace #1775
Conversation
40ace16
to
eef9899
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.
LGTM! Left a question and a nitpick.
bus-mapping/README.md
Outdated
- Iterate over the `ExecutionTrace` itself over | ||
each `ExecutionStep`'s is formed by and check which Stack/Memory&Storage operations are linked to each step. | ||
- Iterate over the [`GethExecTrace`](eth_types::GethExecTrace) itself over | ||
each [`ExecStep`](crate::circuit_input_builder::ExecStep)'s is formed by and check which Stack/Memory&Storage operations are linked to each step. |
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.
nit: not changing line here.
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.
I fixed all the line breaks. I also added a GPT round to improve the readability.
eef9899
to
f998a13
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.
Overall LGTM!
I am checking whether we should add -D warnings
along with cargo test --doc
to assure even warning can be captured.
Since this PR targeting on docs clean up, I suggest we can further restrict warnings on docs test Verify to capture new errors via with below error
|
d58be36
to
9414beb
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.
LGTM! appreciate for taking care of this
Description
We hope the update can reduce confusion.
Issue Link
Type of change
How Has This Been Tested?