Short loop expression will incorrectly become resolved about gojsonsm HOT 2 CLOSED

Here is an example that causes this:

	matcher_test.go:67:   Match Tree:
	matcher_test.go:68:   Matcher Definition:
		match tree:
		  $doc:
		    :elems
		      `friends`:
		        :store $1
		      `index`:
		        :store $2
		    :after-loops:
		      [0] :any in $1:
		        :elems
		          `id`:
		            :ops
		              [0] @ eq $2
		bin tree:
		  [0:0] leaf
		match buckets:
		  0: 0
		num buckets: 1
		num slots: 2

In this case, when any piece of the loop sets bucket 0, it causes IsResolved(0) to return true, but as soon as the loop iteration completes, it then resets it causing the parser to get confused where it is (since short-circuits leave the tokenizer in an inconsistent state).

from gojsonsm.

I think the best way to solve this is to add a special 'loop' entry to the bintree, specifically to fix this issue. Loop stall indexes will point to the first actual loop element, but the loop itself will be represented.

from gojsonsm.