Proposed API for JEP 259: Stack-Walking API

[Mandy Chung]

> On Nov 3, 2015, at 2:08 PM, David M. Lloyd <david.lloyd at redhat.com> wrote:
> 
>> I considered Optional<Class<?>>. I believe it is rare to have a JNI attached thread calling StackWalker::getCallerClass from native.  Most common cases will find a caller class.   Returning an Optional will force most common uses to handle the case if it’s absent.  It’s a tradeoff that I think it’s better to return Thread.class for the JNI attached thread calling getCallerClass in native which would rarely happen.
> 
> I'll say it: I don't think the world will fall apart if it just returns null when there's no caller.  Some might even consider that to be intuitive.

I think there is no real issue to return Thread.class either, right?

Mandy