On 5/8/20 7:52 PM, Henning Thielemann wrote:
> We are talking about the HasCallStack stack traces, yes?
> How is their emission addressed by extending exceptions with stack traces?
The way I understand the proposal, we may be equally talking about DWARF or
profiling cost-center based stack traces.
From a debugging perspective, I guess the developer does not care so much about
which implementation is used, as long as the trace points out the code path
that led to the creation of the exception.
> What are "unintended exceptions"?
> What is an example of an "unintended exception"?
A recent example from my production server:
hPutBuf: resource vanished (Broken pipe)
_______________________________________________
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
