save some bytes per Q-Register creation on the undo stack

 * a table reference was stored in the UndoToken.
 * since there are only two tables at a given moment, this can
   be avoided by having two different undo tokens, one for globals
   and one for locals.
 * Practically, undo tokens for locals are only created for the
   top-level local Q-Reg table since macro calls with locals
   with set must_undo to false since the local table is destroyed
   with the macro return.

0 files changed, 0 insertions, 0 deletions