This is a tricky thing and probably won't matter until it is time to combine queries. So I place this here as a note for myself:
The set_scope will change the scoping for a variable.
Sometimes we need to do that b.c. we define the variable before we define the scope (but perhaps we should not be doing that?)
But sometimes we update the scope, for example, when we go into a Where statement. Perhaps there we should be making a copy of the variable and linking them, but then they have two scopes - so the original guy remains immutable.
The nice thing about doing that is that when you combine queries, and there is something that uses that looping variable without the where, it can. If the scope is updated, then the code will not come out right!
This is a tricky thing and probably won't matter until it is time to combine queries. So I place this here as a note for myself:
Sometimes we need to do that b.c. we define the variable before we define the scope (but perhaps we should not be doing that?)
But sometimes we update the scope, for example, when we go into a Where statement. Perhaps there we should be making a copy of the variable and linking them, but then they have two scopes - so the original guy remains immutable.
The nice thing about doing that is that when you combine queries, and there is something that uses that looping variable without the where, it can. If the scope is updated, then the code will not come out right!