-
Notifications
You must be signed in to change notification settings - Fork 2
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
Deployer says Stack Too Deep #14
Comments
I find the idea of JIT EVM really fascinating. However, it seems that currently, there's no support for JIT execution of generic contract code, so it might be best to wait for native support in Foundry. In the meantime, keeping method chains short can be a workaround to avoid the mc.init("hogehoge");
mc.use(FunctionA);
mc.use(FunctionB);
mc.deploy(); instead of chaining them together like: mc.init("hogehoge").use(FunctionA).use(FunctionB).deploy(); can be effective. |
It sounds good for a bundle, although, could you suggest some ideas on multi-bundle deployment script usecase. The I guess |
I agree that implementing |
Okay, close this issue when you merged that feature. |
I've implemented |
Deployment.s.sol with certain complexity insists it is reached to "Stack too deep".
forge <subcommand> --via-ir
evades that error but compilation is gonna be way too slow.I guess JIT EVM can compress deployment code into LLVM and no stack problem would be shown tho. Let's discuss here.
The text was updated successfully, but these errors were encountered: