tidal shuttle
One of the recent host changes allowed the more widely/completely adopted post mvp wasm features, specially driven by some compilation errors as 1.72 introduced sign extension by default (see #1133320063995367497 message). However I believe that given a scope like smart contracts it might be beneficial to allow for other features that could simplify some stuff.
I know that with soroban already on testnet and soon on mainnet it's difficult that things will change but I would explore the possibility of allowing multi values.
It would allow for reduced env-side allocation interaction (which I believe increases the cost of executing contracts), for instance longer symbols and I suspect even i128s. I would think that one of the reasons why the env doesn't rely on multivalue is that it's not yet fully supported by rust and llvm, but due to a soroban smart contract compilation scope I would argue that the chances of hitting compilation errors like signature mismatches would be unusual on the user's side as most contract solely rely on the soroban sdk.
Tbh I'm not entirely familiar with why rust doesn't have nice support for the multivalue mvp feature yet, so I cannot guarantee that Soroban won't break with this, but seems like a good topic to bring up (likely for next releases of soroban).
What do you guys think?
lunar hearth