As of #98, rose-transpose assumes that no variable defined between an accum and its resolve later gets accessed after that resolve, but it also produces code that violates this assumption by saving those as intermediate values. In the short term, it may be possible to simply avoid generating such code, but really, transposition should work correctly without that assumption.