Support recording method calling another recording method

[mkotsbak]

Typically happens when you call internal private methods and set recording at class level.

Quickfix is probably to exclude recordings on private methods. Better is probably not to start a new recording if a recording in already going on.

[oc]

I think the quickfix is the right fix!

This means public, friendly (package-local, package-private, (friendly is; and has many names:)) and protected methods in the first place?

The characterization should normally be the methods used by others :)

[mkotsbak]

Well, I doubt the quickfix is any quicker. I think it will be as easy to just let the ongoing recording continue if we hit a recording method when already recording, and it might solve other similar issues.

[oc]

I think I misunderstood the issue, I agree it might be better to just record one at a time, however that might not capture obscure usages of static/mutable state, etc if we isolate the recordings (?). I guess we should not put too much mind into optimizing this just yet. :)

[mkotsbak]

I think we fast will get some data on the actual cases if we get a usable version.