core

core copied to clipboard

Component

sol! macro

Describe the feature you would like

As ethers-contract allowed, alloy-contract should allow outputting the generated code to a file to allow manual inspection.

This allows anyone curious about how their specific contract had code generated (exact function API/type signatures) trivially inspect it, and can make the sol macro functionality a one-time dependency (to output to code once) or solely a build-time dependency.

Additional context

No response

You can inspect any generated code with cargo-expand.

I might still add it for the build script use case though.

AFAICT, this would be... 'trivially' resolved if SolMacroExpander were made public (enable functionally calling it, like one can with Abigen). I'm unsure I want to make a PR with that amount of an API commitment though. Happy to hear opinions/suggestions.

EDIT: SolMacroExpander would have to be moved to a new crate/into the sol-macro-input crate, unless the file exporting was part of the macro (and not functional like with Abigen) :/ I did get a PoC of what I'd like though.

after #626 this should be pretty straightforward. cc @yash-atreya