@samth I checked the trace after the fix and it seem to have solved the issue I observed in pnpoly benchmark, the new pycket’s trace is now identical to the old pycket’s trace for that particular benchmark

Also I seem to have pushed it to the wrong branch