Harry Solovay

`Rune.de`

1

A utility to simplify destructuring runes from runes. ```ts const abc = Rune.tuple([a, b, c]) const [a, b, c] = Rune.de(abc) const xyz = Rune.rec({ a, b, c }) const...

@tjjfvi's suggestion: ```diff class Rune { constructor(readonly _prime: (batch: Batch) => Run, readonly ..._arguments: A) {} // ... + clone(){ + return new this.constructor(this._prime, ...this._arguments) + } } ```

Perhaps a similar interface to [that of `scale-ts`](https://github.com/paritytech/scale-ts/blob/5a6465ac7bf6135f12ef5392a6782343b7f88697/common/metadata.ts)? I'd imagine this is how we'll tackle pretty-printing, #521 and serialization.

Inspiration: - [paritytech/substrate-debug-kit](https://github.com/paritytech/substrate-debug-kit) for inspiration. - assertion of specific events emitted

What is the minimal setup for pattern lib development. How does one consume a pattern lib? How do import maps play in? What conventions do we want to define?

A document(s) comparable to [the AWS CDK's design guidelines](https://github.com/aws/aws-cdk/blob/v1-main/docs/DESIGN_GUIDELINES.md) which touches on how to craft an idiomatic Capi pattern lib.

@tjjfvi pointed to https://substrate.stackexchange.com/questions/2552/how-to-calculate-the-optimal-tip-for-substrate

move `dbg` onto `Rune`

1

So that we don't need to always `.into(ValueRune)` while debugging

implement consumption of old metadata versions

1

How do we want to handle old metadata versions? Ideally this won't involve re-implementing common codecs for each version. However, this is quite important for interacting with archival nodes, as...

A CI check that ensures all `moderate`d files are up-to-date