foundry-huff
foundry-huff copied to clipboard
huff-language
A Foundry Library for compiling, debugging, and working with Huff contracts in Solidity.
The following warnings are displayed when `forge test` is run. This PR will modify so that these warnings are not displayed. ``` warning[2519]: Warning: This declaration shadows an existing declaration....
Related: #27 I found the `_` prefix and these `a` prefixes while creating #27. Unlike #27, this PR is not important, but I'm reporting it. As https://github.com/ethereum/solidity/pull/12680 states, a `_`...
**Problem** Currently it is not possible to change the `msg.sender` (op: `caller`) of the create transaction for Huff contracts, when using `HuffConfig` / `HuffDeployer`. This is necessary when testing contracts...
So that others who want to improve this package know how to set up their dev environment. This should have: 1. How to setup dev environment 2. A code of...
would be nice to not be forced to use `src` as root folder for huff contracts. just removing the `src` path prefix is ok, even better, set a path prefix...
Hi there I was wondering if there was anyway to use foundry's debug console (to track the stack, opcode etc) with huff? I have deployed the huff contract and tried...
if `deploy()` fails due to a compilation error, we should return the error message. i assume this is possible with some ffi magic
Currently, running ` HuffDeployer.broadcast("T");` would fail: ``` │ ├─ [0] VM::prank(HuffConfig: [0xC7f2Cf4845C6db0e1a1e91ED41Bcd0FcC1b0E141]) │ │ └─ ← () │ ├─ [0] VM::ffi(["rm", "src/__TEMP__abfzyqnaxzhwmracwudpzrzbuoyhhizhT.huff"]) │ │ └─ ← 0x │ ├─ [0]...
Deploying a huff contract through `forge script` fails with the following trace: ``` Traces: [2245499] → new Deploy@0x7FA9385bE102ac3EAc297483Dd6233D62b3e1496 └─ ← 11154 bytes of code [2160044] Deploy::run() ├─ [2059491] → new...
Metadata
Owner
Metadata
A Foundry Library for compiling, debugging, and working with Huff contracts in Solidity.