Issues to file / tackle Before a big announcement (but it’s fine if it’s public) move combinators.util and combinators.{tensor,trace}.util into separate code base review old tests discovery rerun Long-term (maybe worth filing as issues) tutorial Standard VI: inclusive / exclusive simple regression RV.resamplable should be handled at a higher level objectives api documentation do we actually need a copy of the trace in our substitution context? Might cause a dangling ref.