refcell

> That's amazing, I'm wondering if there shouldn't be a separate huff testing framework before testing gets too big, unless you wanna keep it lightweight! > Are you counting gas...

RFC @clabby

This is an interesting issue. With the current setup, the `msg.sender` is set as the caller as described in [forge-std/src/Vm.sol](https://github.com/foundry-rs/forge-std/blob/master/src/Vm.sol): ```md // Has the next call (at this call depth...

Na deployer address isn't used. Can also be: ```solidity function runTestConstructorCaller() public { HuffConfig config = HuffDeployer.config(); IRememberCreator rememberer = IRememberCreator( config .set_broadcast(true) .deploy("test/contracts/RememberCreator") ); assertEq(rememberer.CREATOR(), address(this)); } function testConstructorCaller()...

> whats the relationship between this repo and huffmates. for example how will the erc20 in this repo differ from huffmate? which repo do we encourage contributors to use? This...

Further - I think it's important to have both as one serves as a way to fully understand huff contracts, whereas the other (huffmate) serves as a devtool. Especially given...

> thats a v clear explanation. so if thats the case should these ctrcts import the huffmate "abstract" ctrcts? Yooo, yes that's a great idea. Will implement in this branch....

Reinstalling [`wasm-pack`](https://rustwasm.github.io/wasm-pack/installer/) did the trick for me: ```bash curl https://rustwasm.github.io/wasm-pack/installer/init.sh -sSf | sh ```

> We should delay this as risc0 guys had breaking change with llvm17 so would wait couple of months for new rust release as it is not a big inconvenience...

I wonder if we could use interfaces to assert the behavior of at least a portion of the functions in the script.