Minimal test case for super() bug in MontageReviver

[asolove]

+100 points to @aadsm for this discovery: a bug caused by a strange loop!

The problem

MontageReviver is a subclass of Reviver. When you call MontageReviver#reviveRootObject it calls super, which resolves to Reviver#reviveRootObject. That method then calls other methods on the object, which eventually wind their way around to calling MontageReviver#reviveRootObject again. When we reach the super call the second time, which is still nested inside the call stack for the first time, the super context thinks we're trying to call the parent of Reviver, rather than of MontageReviver, and is thus a no-op.

Possible fixes

1. Laugh at this strange problem and content ourselves with manually calling Reviver.prototype.reviveRootObject instead of having the convenience of super in this specific case.
2. Fix super to work in cases like this. When we call super() from inside Class#method, we could wrap Class#method in a decorator. Then if it is called again within itself, the wrapper resets the super context just for the duration of the inner call.

[francoisfrisch]

Fix super to work in cases like this. When we call super() from inside Class#method, we could wrap Class#method in a decorator. Then if it is called again within itself, the wrapper resets the super context just for the duration of the inner call.

Would the decorator be left in place? If it isn't this could be expensive... if it is this could mess up some references.
A could problems that would need to be solved to leave it in place

1. this.super() uses the reference to the function itself I believe, this will need to be handled.
2. If the function is assigned to another object's property it will need to be able to detect that and recover.

[asolove]

Yeah, I'm not sure if the decorator method is possible. I've been hacking at it for a bit and changing to a wrapped method breaks a lot of other things even before we get to your objections.

In addition, since we maintain the super chain inline with the call stack, I've noticed that super doesn't work with anything async...