IGI-111
IGI-111
Closed in favor of https://github.com/FuelLabs/sway/issues/5512
>This makes operations involving dynamicly-sized runtime allocation somewhat harder/constly, but I don't feel think code is common in smart contracts anyways. I don't think this is a reasonable assumption to...
Yeah deprecation warnings sounds like a good way to do it.
It seems like the costly part here is actually building the CFG. Especially maintaining the `decls` hashmap and hashing all those idents, do we really need it?
A few nitpicks, but LGTM
> For `test`, I think we may be able to re-use the engines across tests, but not really sure if we want to do that, given it means each individual...
This PR has gone for a long time already. I'd say we merge these changes to a stable state and move to the one slab per module approach in a...
I think the reasoning here is sound, the new error seems indeed most appropriate for sequential shadowing. I think it's probably clearer to go with distinct error messages for each...
These should be added to https://github.com/FuelLabs/sway/blob/master/test/src/e2e_vm_tests/test_programs/should_fail/asm_disallowed_opcodes/src/main.sw should they not?
Well it looks like we have a test that enforced the rule that you're not allowed to use control flow opcodes in asm blocks, which I guess is why we...