These isn't a public api to get the parent of a MortarScope. about mortar HOT 1 OPEN

Yeah, we should probably add that. We've been hesitant to do so because the "only" uses we've found have been for debugging output, and it seems more prone for abuse in production code.

In the meantime you can hack around the lack by introducing your own peekaboo class in the mortar package. E.g.

package mortar;

public class ScopeSpy {
  public static MortarScope parentScope(MortarScope mortarScope) {
    return mortarScope.parent;
  }
}

from mortar.