Alexander Theißen

> When we then have `v15` as stable metadata, we can introduce `metadata-v14`. But adding a feature for old metadata would only make sense if it this substantially reduces compiles...

Don't merge we need to do another bench all after https://github.com/paritytech/substrate/pull/13595 is merged.

bot bench $ all

bot bench $ all

Yeah if `O4` and `O2` are similar we can just go with `O2` which is more conservative and faster. But the optimizations don't seems to help overall. They are supposed...

Neither this PR nor under the new wasmi 0.28 in #13312 we saw any performance improvements with wasm-opt. On the contrary: The performance regressed. This is why we do not...

> There is still the runtime step to transform the static metadata definitions into the serializable form. I know that this is done at runtime right now. The point is...

> Metadata is composed of type information generated by `scale-info`, which at its core uses [`std::any::TypeId::of`](https://doc.rust-lang.org/stable/std/any/struct.TypeId.html#method.of) to uniquely identify types and build up the type lookup registry. This is only...

I thought multiple times that just having the examples in the same workspace as ink! itself would be nice. But there is a reason why this isn't possible. And I...

Yes. I see no reason why not to add it.