Feat/eugene/postcard bindgen

0xterminator commented 1 month ago

[Link to related issue(s) here, if any]

[Short description of the changes.]

Checklist

[ ] Breaking changes are clearly marked as such in the PR description and changelog
[ ] New behavior is reflected in tests
[ ] If performance characteristic of an instruction change, update gas costs as well or make a follow-up PR for that
[ ] The specification matches the implemented behavior (link update PR if changes are needed)

Before requesting review

[ ] I have reviewed the code myself
[ ] I have created follow-up issues caused by this PR and linked them here

After merging, notify other teams

[Add or remove entries as needed]

[ ] Rust SDK
[ ] Sway compiler
[ ] Platform documentation (for out-of-organization contributors, the person merging the PR will do this)
[ ] Someone else?

xgreenx commented 1 month ago

What is the purpose of this PR?=)

0xterminator commented 1 month ago

What is the purpose of this PR?=)

It is just a draft, I am experimenting with adding postcard to js bindings.

xgreenx commented 1 month ago

Why do you need it?=) You can use from_json and to_json function in WASM, if you want to

0xterminator commented 1 month ago

Why do you need it?=) You can use from_json and to_json function in WASM, if you want to

I know, but what we want to see is whether we can attach this crate https://github.com/teamplayer3/postcard-bindgen so we generate for all structures that we want to stream over nats ser/deser functionalities using postcard and also have an auto-generated npm package for our ts-sdk (fuel-systems_) in order to have 1:1 serialization/deserialization of the same structures.

0xterminator commented 1 month ago

Closing as this research did not lead to the desired effect @pedronauck

FuelLabs / fuel-vm