replace definition of error with errorWithStackTrace

Christopher Allen cma at bitemyapp.com
Mon Dec 1 04:39:20 UTC 2014


+1 - I would be very happy if this happened.

On Sun, Nov 30, 2014 at 10:09 PM, Mark Wotton <mwotton at gmail.com> wrote:

> having just spent a day tracking down a really uninformative error in
> Cabal, I'm all for this.
>
> On Mon Dec 01 2014 at 11:08:35 Carter Schonwald <
> carter.schonwald at gmail.com> wrote:
>
>>
>> http://hackage.haskell.org/package/base-4.7.0.1/docs/GHC-Stack.html#v:errorWithStackTrace
>>
>> has been in GHC for for >=1 major version,
>> and for normal builds, acts just like error, BUT, when an error is thrown
>> in a profiled build, it appends a stack trace with some basic source
>> location data to the end of the error message!
>>
>> I think this change would benefit many!
>>
>> My current understanding is that the DWARF based approach to stack traces
>> wont make it into  GHC 7.10 , and while this variant would only provide
>> extra info in profiling builds (and strictly less than the dwarf work), its
>> something that can definitely be done in a single small patch that could
>> easily be swapped out for that improved approach once it lands.
>>
>>
>> discussion period: 2 weeks unless theres a clear unanimous agreement to
>> make the change ASAP, OR if the stack trace error stuff is landing in 7.10
>> and I'm misinformed!
>>
>> cheers
>> -Carter
>>
>> _______________________________________________
>> Libraries mailing list
>> Libraries at haskell.org
>> http://www.haskell.org/mailman/listinfo/libraries
>>
>
> _______________________________________________
> Libraries mailing list
> Libraries at haskell.org
> http://www.haskell.org/mailman/listinfo/libraries
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/libraries/attachments/20141130/69db02ff/attachment-0001.html>


More information about the Libraries mailing list