runtianz

> Nonetheless, I do not want to add Serialize, Deserialize for the file format types. These types have a hand rolled serialization format as defined in the serializer/deserializer. I do...

> > I really would love to have round trip serialization of the exact CompiledModule. Even though we have debug prints, they are not parsable in Rust. This makes it...

> We already do this in Rust tests by just constructing the compiled module in Rust syntax This was a bit hard to work with our transactional test framework. We...

Was wondering if moving the resolver to vm-types is the best way to clean up the logic here, as it could potentially break external dependencies (not in our own repo)....

> I tried using an associated type before, the problem with this approach in my opinion as we have to keep a phantom error type inside StorageAdapter and other "storage"...

Are we going to bundle this change with type builder then?

> Is this error triggerable? This error shouldn't be triggered as long as the VM remains single threaded.

Was wondering when those metadata can be changed? IIUC they should stay immutable? Am I missing anything?