Guillaume Thiolliere

> Event parameters are unnamed and we are currently relying on non-standard syntax in docs comment to document it. if I don't missundertand this should be fixed, we can now...

> > cc @thiolliere > > We were already thinking about making a pretty large change to events in Substrate to help with PoV size, and isolate them from other...

I think modifying Event codec implementation so that it is decodable as `Vec` makes complete sense, we do that for some types already. It can be done in construct_runtime when...

is paritytech/substrate#8615 an ok solution all in all ? Or otherwise it shouldn't be difficult to implement `EventRecord` codec so it is decodable as a `Vec`. Or implement `Event` codec...

It seems scale-info metadata should solve this issue, we could also make event decodable as a `Vec` which is implemented in this PR https://github.com/paritytech/substrate/pull/9738 but it is an important breaking...

Thanks for the report. (happy to see arch users, I was once but now I am on debian stretch) First we can try to run with less window option. The...

we could also take into attribute the optional ident given to export_tokens: ```rust #[use_export_tokens(MyIdent)] use foo::MyStruct; ```

but AFAICT we don't need the counter, we can re-export from the locally defined re-export without counter. for ```rust #[export_tokens] pub struct MyStruct; ``` it generates in scope the items...

I meant the latter. But I see your point now. I understand what you meant. In case they do `#[export_tokens(Foo)]` and there is no item `Foo`, then they cannot do...

> * For an immediate re-run of the tool, I would want it to "fail" fast with status information rather than restart larger processes and downloads. `cargo risczero install` will...