Open xgreenx opened 7 months ago
@xgreenx Contextually, we used to have a single multi-call .sw
script that we used for everything. One of the problems was that it could handle a limited number of calls. Then, we replaced it with its dynamic counterpart using WASM fuel-asm
and following how the Rust SDK was doing it.
Do you think we should return to having a statically compiled .sw
script in this sense?
Or just change how we assemble it dynamically before calling it?
@arboleya I'd like to reassign this to library
. IMO this will likely be handled by a script loader in a similar way to the new loader contract bytecode generation, that should live inside the script
or program
packages.
@arboleya Should we move this back to the backlog? It seems we still lack some information about how to proceed here
Duplicate of the https://github.com/FuelLabs/fuels-rs/issues/1267, but for the TS SDK. It is better to have only one issue with the description since both SDKs have the same problems.