core
core copied to clipboard
alloy-rs
High-performance, well-tested & documented core libraries for Ethereum, in Rust
### Component sol! macro ### Describe the feature you would like Currently this is ignored, except for state variables: https://github.com/alloy-rs/core/blob/c8dece2715151928ea33819ef5e7f0f57050256a/crates/sol-macro/src/expand/mod.rs#L267-L282 ### Additional context - Should we ignore it always? -...
Add a library that outputs valid and/or properly formatted solidity based on the Solidity AST representations my point is that "converting type specifications to solidity strings" is probably a common...
### Component syn-solidity ### What version of Alloy are you on? Latest ### Operating System None ### Describe the bug - Operand order in `Expr::*Op` may be incorrect - `delete...
I think this can be done in another PR, since we don't handle any type of function (constructor, fallback...) other than literally `function` _Originally posted by @DaniPopes in https://github.com/alloy-rs/core/pull/153#discussion_r1242571988_ Similar...
Wrap the visitor macro impl with [`paste::paste! {}`](https://docs.rs/paste/latest/paste/) and wrap function names: `[]`
### Component json-abi ### Describe the feature you would like Add a borrowed version of all `json-abi` types, which implement `ToOwned`. Ideally methods are implemented only once, with the owned...
To consider: should we error if there are too many topics in the iterator? _Originally posted by @prestwich in https://github.com/alloy-rs/core/pull/83#discussion_r1225887774_
Custom types are Solidity paths, and currently we panic if it's longer than 1 ident.
Can users use `.into()` the way they'd expect
## Motivation Lighthouse is currently migrating our code base and relevant dependencies to `alloy_primtives`. During the migration we've come across some circular dependency issues between the `ethereum_ssz` and `alloy_primitives` crates....
