On 5/12/20 10:55 PM, Henning Thielemann wrote:
> "This operation may fail with:
>
> * ResourceVanished if the handle is a pipe or socket, and the reading end is
> closed."
>
> That is, ResourceVanished is part of the public interface and in no way
> unexpected (or what "unintended" may be). I
On Fri, 8 May 2020, Ben Gamari wrote:
Henning Thielemann writes:
We are talking about the HasCallStack stack traces, yes?
How is their emission addressed by extending exceptions with stack
traces?
HasCallStack stack traces are one type of backtrace that the proposal
supports. However,
On Fri, 8 May 2020, Ben Gamari wrote:
We can debate whether partial functions like `fromJust` should exist; however,
the fact of the matter is that they do exist and they are used.
That's not my point. I say: fromJust on Nothing is a programming error,
ok. We must debug this. HasCallStack
On Fri, 8 May 2020, Niklas Hambüchen wrote:
What are "unintended exceptions"?
What is an example of an "unintended exception"?
A recent example from my production server:
hPutBuf: resource vanished (Broken pipe)
Ok, I lookup the Haddock comment of hPutBuf and it says:
"This operation
This would also help to resolve
https://github.com/digital-asset/ghcide/pull/350#discussion_r370878197,
where we cannot get ApiAnnotations and Haddock comments at the same time.
On Tue, 12 May 2020 at 18:38, Karpov, Mark wrote:
> Hello,
>
> I'd like to mention that it would be nice if this
Hello,
I'd like to mention that it would be nice if this patch
https://gitlab.haskell.org/ghc/ghc/-/merge_requests/2377 could be included
in 8.12. Right now we have a few issues that Ormolu users have reported
which stem from how Haddocks are parsed by GHC (e.g. that issue when a file
starts with
