| 2303 | 🙂 | Suggestion | It would be nice if there was a way to control the scope of the Unlock instruction. Putting one inside a sub-behavior invoked via a Call instruction causes the entire behavior to be affected by the Unlock instruction. If end of a Call instruction reset the Unlock state, that would ease the cost of utilizing Unlock. Alternatively, if there was a matching Lock instruction, we could manually limit the scope.
As it is, having to add Wait instructions to every piece of a big behavior makes it hard to embrace using an Unlock instruction. Even if it wouldn't be a huge problem due to how many instructions can be run between Waits. | | 2023-09-10 21:29:05 |