Plugin for controlling whether or not to fill in stacktraces

[ZacSweers]

Resolves #117

This implements support for controlling whether or not OutsideLifecycleExceptions fill in their stacktraces. This is a potentially expensive operation that is often used just for signaling, so we can save a little perf here.

[tonycosentini]

Is it possible to add more details about what the specific performance improvements are?

Also +1 to Leland's comment about including example stacktraces to demonstrate the differences.

[ZacSweers]

Details beyond

This is a potentially expensive operation that is often used just for signaling, so we can save a little perf here.

?

I’ll add an example, but bear in mind the point is that there is no trace, just the exception name and message. In a conventional “stacktrace”, the difference is that you effictively only get the first line here

[tonycosentini]

What is expensive? Just creating the stacktrace itself? Whatever it is, just mentioning it might be useful.

[ZacSweers]

Yes, fillInStacktrace() is (this is detailed in the linked issue as well)

[tonycosentini]

Is it worth adding the same details to the javadoc?

[ZacSweers]

Beyond what's already there?

Disabling them, if you don't care about the stacktraces, can result in some minor performance improvements.

[tonycosentini]

Yes, beyond what's already there.

[ZacSweers]

(talked and the javadoc is fine as-is)