Isolated Methods JEP

[Jochen Theodorou]

On 13.08.2016 00:54, John Rose wrote:
[...]
> Probably the IM is just a faster, more compact way to make something you
> could also have made by spinning MH's together.  If someone figures out
> what an IM can do that you can't also do with MethodHandles.* methods,
> I'm very eager to hear about it.  (And I'll probably want to take it
> away, or else add a new MHs API point.)  Mainly, an IM gives you control
> over packaging and backtrace structure.

how would throwing and catching exceptions behave there? Can I do these 
without showing the IM on the trace? Because... unless it got changed in 
the meantime... using a MethodHandle that does catch Exceptions 
introduces a trace element (and quite the speed penalty)

bye Jochen