We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There’s an easy solution that’s purely on the WASM side: We could generate
class AuctionCreatedEvent extends EthereumEvent { id(): Bytes { return this.params[0].value } assetId(): H256 { return this.params[1].value } seller(): string { return this.params[2].value } }
When people then write handlers like
handleAuctionCreatedEvent(event: AuctionCreatedEvent) { ... }
they could use event.id(), event.seller(). (edited) That requires no magic at all in Rust.
event.id()
event.seller()
We could try using generics like
Event1<T> Event2<T,U> Event3<T,U,V> ...
and write Asc type conversions for the. The names of the parameters don't matter, just their order and their types.
The text was updated successfully, but these errors were encountered:
Jannis
No branches or pull requests
WASM-only solution
There’s an easy solution that’s purely on the WASM side: We could generate
When people then write handlers like
they could use
event.id()
,event.seller()
. (edited)That requires no magic at all in Rust.
Rust solution
We could try using generics like
and write Asc type conversions for the. The names of the parameters don't matter, just their order and their types.
The text was updated successfully, but these errors were encountered: