Egregoros

>tests
My code isn't even breaking it's a style thing. I specifically told it to avoid classes and just write procedural code but I ended up with all these "globals" declared in every function which are allegedly bad.
I don't really get why yet, but again, maybe I am just too bad of a programmer. No idea.
Grok keeps telling me it avoids problems but when I ask which ones, it's stuff like "if you use global foo and you forget the keyword once it will create a local variable instead and assign that."
Okay. Why? Why is that good? idgi

>types
another thing that I would rather have by default, but hasn't been an issue in my simple script here, yet.
My agent hasn't been off track with that yet. It's only a thousand lines (way too much if you ask me) at this point. Probably fits context easily.

my naive answer would be isn't that more about control flow than the variable being global or not?
Calling an object that encapsulates the state doesn't make it more understandable than just having a global edit_mode_toggle and toggling that within program flow...

>, there is no duplication, the function chain compiles into an imperative loop
this is more of a stack overflow/google stupid question I guess, but if the function is just made once and the language internally just passes a pointer to the variables it needs on execution, isn't that just a bit of syntactic sugar around doing that yourself? where's the closure part come in?
I got a bit less sleep so apologies if this is a dumb thing to ask