A v3.8 / v4.0 / yuqk vector tuple assignment issue.

I've been working through more tuple (batch) ID assignment test cases. In the documentation I've been able to turn up for the original tuple capability, there was this bit related to assigning components of vectors to individual identifiers:

---
In addition, a similar syntax extension has been added for easier assignment of vector components to individual variables:

    #declare < ID1, ID2, ... > = VECTOR_EXPR;

This statement is fully equivalent to:

    #local TEMP = VECTOR_EXPR;
    #declare ID1 = TEMP.x;
    #declare IDY = TEMP.y;
   ...

except that the new syntax does not actually define a local variable named TEMP.  The terminating semicolon is mandatory.
---

All seems to work except the mandatory semicolon bit is not enforced by the parser!

This means the following code runs without complaint, but incorrectly.

    #declare <A0,A1,A2> = <3,2,1>; // This works.
    #declare <A0,A1,A2> = <1,2,3>  // This only appears to work.
    #debug concat("A0 = ",str(A0,3,1),"\n")
    #debug concat("A1 = ",str(A1,3,1),"\n")
    #debug concat("A2 = ",str(A2,3,1),"\n")

    #error "Stopping at parse test end\n"

The exposure made worse because in other applications, the tuple ID assignments treats the trailing semicolon as optional.

Bill P.