replace definition of error with errorWithStackTrace

Michael Snoyman michael at
Tue Dec 2 09:08:23 UTC 2014

On Tue Dec 02 2014 at 11:05:27 AM Simon Peyton Jones <simonpj at>

>  +1, as I don't see a downside. However, I don't think this change is a
> sufficient change as long as stack traces are only available for profiled
> builds. I still wish something like rewrite-with-location[1], which even
> addresses explicit stack traces directly[2]. IIRC, last time that feature
> was brought up for discussion, it stalled due to disagreements on the right
> design.
> I think we have something of a consensus forming around
> see #9049.   It’s simple, non-invasive, and predicatable.  It does need
> someone to implement it though.   Simon Hengel is thinking about
> implementing it.  (He is the one who also suggested “rewrite with
> location”).
> So I think we are stalled not so much on design but on implementation.
> Simon
That's great news, thanks for the update. I was not aware of that proposal.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the Libraries mailing list