On 02/09/2013 15:08, Jörn Huxhorn wrote:
:
Nick also explained a performance issue in Thread#getStackTrace() and
Throwable#getStackTrace(). Keeping that in mind, I'm not sure if going for "start
small" (i.e. leaving that issue alone) would be a wise decision.
It was a non goal of JEP 176 to provide @CallerSensitive as a public
API. So the suggestion to start out small was to leave that out and
focus on some of the use-cases initially. I don't think this suggestion
is unreasonable as it allows the less controversial part to move forward.
-Alan.
