Skip to content
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

Workshop -> nit picks and questions #125

Closed
wants to merge 1 commit into from
Closed

Conversation

nuke-web3
Copy link
Contributor

WIP - probably a DO-NOT-MEREGE but other smaller PRs will reference this one

I will comment on things as I go, and @ people to ask things in this PR along the way.

@nuke-web3 nuke-web3 self-assigned this Jun 28, 2024
@nuke-web3 nuke-web3 added documentation Improvements or additions to documentation question Further information is requested labels Jun 28, 2024
@@ -66,7 +66,7 @@ Your new project consists of:
- Builds for zkVM program, the publisher app, and any other Rust code.

```sh
cargo build
cargo build --release
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Is the only reason we must run this first is because forge is looking to get an Elf.sol that this builds?

Or should we be optimizing here for the forge b next?

Copy link
Contributor

Choose a reason for hiding this comment

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

Indeed cargo build generates the ImageID.sol and Elf.sol files, which is the primary reason it needs to run first. I don't know of any way to achieve this just by running forge build or forge test.

I don't see any reason to run with --release, since the performance is not an issue in client-server mode.

Copy link
Member

Choose a reason for hiding this comment

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

Also --release takes a lot longer to build, so if you're in client/server, it might not be worth it.

@nategraf
Copy link
Contributor

nategraf commented Aug 5, 2024

I'm going to go ahead an close this PR, since I think we discussed we will not merge the change in it.

@nategraf nategraf closed this Aug 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation question Further information is requested
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants