metavar_spans is a piece of global data that lives in SessionGlobals, it is similar to hygiene data in the same SessionGlobals.
This table is populated during macro expansion and after that it doesn't change.
Data from the table can be read from any query that performs the span1.to(span2) operation.
This table is clearly a piece of untracked data.
We also cannot querify accesses to it by passing tcx to all span1.to(span2) operations.
I suspect the whole table should be hashed at some point after macro expansion so it becomes an initial input to the query system.
metavar_spansis a piece of global data that lives inSessionGlobals, it is similar to hygiene data in the sameSessionGlobals.This table is populated during macro expansion and after that it doesn't change.
Data from the table can be read from any query that performs the
span1.to(span2)operation.This table is clearly a piece of untracked data.
We also cannot querify accesses to it by passing
tcxto allspan1.to(span2)operations.I suspect the whole table should be hashed at some point after macro expansion so it becomes an initial input to the query system.