Nicole L

What's the use case for opting out of the SDK-provided traits for serialization? I get disabling vtable serialization so that they can control when serialization happens, but what value would...

One part of this might be to allow for code generation to happen as part of the `build.rs` script. Right now, users have to manually execute a command in order...

Giving it some more though, I think we should be able to distribute schema files via crates.io: * When publishing a crate, [you can include arbitrary extra files](https://doc.rust-lang.org/cargo/reference/publishing.html#packaging-a-crate) in addition...

#72 brings up an interesting problem for this approach to code generation: We'll need to handle schema files that reference external types. This needs to be addressed in two ways:...

Another thing to consider: How do we allow for custom code generation (e.g. for GDKs to have custom code generation) if code generation is baked into each crate that provides...

#117 may provide the answer to the previous question: If we provide some mechanism (maybe WASM-based) to safely inject custom code generation logic, upstream crates can also potentially load the...

There's a nifty crate for making this easy to do, would allow us to write less code generation on our end: https://github.com/nrc/derive-new

I'm not sure doing serialization as a macro makes sense, at least not with how we handle schema data in the SDK right now. Using a macro (specifically a [custom...

The idea of using WASM as a way of providing compile-time extensions has been coming up elsewhere in the Rust community, too. We should check out [watt](https://github.com/dtolnay/watt) and see if...

I would request that the cookbook demonstrate how to asynchronously load a file from disk, assuming there's a way to do so. As far as I know, there's currently no...