| 2068 | 🙂 | Suggestion | Behaviour desperately need a static variable setting. Maybe an instruction that works like copy and set number but will not wipe the variable just like top level variables that persist when the behaviour ends and restarts naturally.
Certainly not for all subroutine variables and I get that you would want to have it instanced per call site of that subroutine but honestly even if its global across all calls to that subroutine and not instanced to the call site it would be super helpful as the only other way I can think of is to always have like cache output variables that must be propogated at least up to top level behaviour variables if not params so they persist across runs & calls but that requires propogation of what can end up a heap of variables with little to do with the higher subroutines, to say nothing of forcing the top level behaviour to consume more variables/params and figure out what if anything to do with them... | | 2023-09-04 17:54:08 |