Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

via ir build #22

Merged
merged 11 commits into from
Feb 20, 2024
Merged

via ir build #22

merged 11 commits into from
Feb 20, 2024

Conversation

QGarchery
Copy link
Contributor

@QGarchery QGarchery commented Feb 20, 2024

Continuation of #21

@QGarchery QGarchery self-assigned this Feb 20, 2024
@QGarchery QGarchery marked this pull request as ready for review February 20, 2024 12:20
@QGarchery

This comment was marked as outdated.

@QGarchery QGarchery closed this Feb 20, 2024
@QGarchery QGarchery reopened this Feb 20, 2024
@QGarchery QGarchery requested review from MathisGD, a team, adhusson, Rubilmax, MerlinEgalite and Jean-Grimal and removed request for a team February 20, 2024 13:06
Copy link
Contributor

@MathisGD MathisGD left a comment

Choose a reason for hiding this comment

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

  • tests work with Metamorpho compiled with the foundry config of the Public allocator
  • and forge build --size skips Import, so Blue and Metamorpho such that it doesn't throw an error

just imo in the readme we could write that in the tests metamorpho isn't the same as the one deployed onchain for this reason (it's ok but let's write it somewhere, as it could cause discrepancy in gas test or something)

@QGarchery QGarchery merged commit 3e02241 into feat/flows-and-eth-fee Feb 20, 2024
1 check passed
@@ -30,10 +30,10 @@ jobs:
- name: Run Forge build
run: |
forge --version
forge build --sizes
forge build --sizes --skip Import
Copy link
Contributor

Choose a reason for hiding this comment

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

Skipping Import could be added to a foundry "build" profile so the whole build config has a single source of truth (i understand it may be overkill for now because there's only 1 option and 1 place where it's used)

As a new dev here, i would forge build ; is it what's expected?
Otherwise we could argue that having a build profile makes it clearer how this repository is intended to be built

Copy link
Contributor Author

@QGarchery QGarchery Feb 20, 2024

Choose a reason for hiding this comment

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

It's the same in the end, all will be built the same way. Skipping imports just delays the build of dependencies to when actually running tests (delaying is only useful here because we check the sizes)

Copy link
Contributor

Choose a reason for hiding this comment

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

forge build builds correctly the public allocator, so that's ok for me

@MathisGD MathisGD deleted the chore/via-ir-build branch February 20, 2024 13:37
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants