Thanks for writing this up!
I was a user of SafeHaskell briefly in 2011-2012, and it certainly has
theoretical benefits. That said, though, I agree that the balance of the
cost-benefit analysis is solidly against it, and I would much rather ease
the burden of GHC and library development than
Just to satisfy my curiosity here, when talking about backtraces here, are
you talking about a lexical call stack, or an execution stack?
On Thu, Nov 18, 2021 at 11:24 AM Richard Eisenberg
wrote:
>
>
> On Nov 18, 2021, at 10:29 AM, Ben Gamari wrote:
>
> At this point, for backtrace support I
On Fri, Oct 8, 2021 at 10:51 AM Ben Gamari wrote:
> In my mind the fundamental problem with this approach is that it means
> that a program's acceptance by the compiler hinges upon pragmas.
> This is a rather significant departure from the status quo, where one
> can remove all pragmas and still
Oops, I meant to include this URL:
https://github.com/google/codeworld/issues?q=label%3Aerror-message+%22code.world%2Fhaskell%22
is the full list (including closed issues) of cases where someone has
reported a misleading error message at code.world/haskell
On Tue, Sep 7, 2021 at 9:03 PM Chris
Hi Richard,
One thing that I've done with CodeWorld for years now was to integrate
reporting poor error messages into the core workflow by adding a report
button on the compiler output directly in the tool. This integration files
github issues with a special tag for error messages. Because
Yikes, this is going to break nearly everything. Definitely good to let
people know.
On Sun, Jun 20, 2021 at 7:43 AM Ben Gamari wrote:
> Harendra Kumar writes:
>
> > I see the following errors when compiling with ghc head version:
> >
> > $ ghc-stage2 --version
> > The Glorious Glasgow
This might be in the "ship has sailed" territory, but I'd like to bring it
up anyway.
https://github.com/ghc-proposals/ghc-proposals/blob/master/proposals/0287-simplify-subsumption.rst
says:
Suppose GHC lacked all four features, and someone proposed adding them.
> That proposal would never leave
Viktor,
Sorry you had a bad experience. Perhaps it will help to know that these
bans are automatically done by bots to prevent the channel from being
flooded by nefarious users. That you were caught by it was just a
false positive because you triggered the flooding detection. It doesn't
mean
No, unfortunately, this is not resolved. The link here is a fictitious
whitewash of events posted by the person who conducted the hostile takeover
of Freenode. At the moment, the state of Freenode is that it's still
operating as an IRC network, but the volunteer staff who have operated the
On Fri, May 21, 2021 at 2:11 AM Baldur Blöndal wrote:
> > encouraging the use of a standalone signature for type declarations
> where at least one parameter of the datatype does not have kind Type.
>
> So Dict, Eq both get a sig but Fix and Either do not?
>
> type Dict :: Constraint -> Type
>
Thanks, Richard. This is awesome!
For my use case, the more exciting possibility would be to interact with
error messages from JavaScript. For this reason, I'd definitely love to
see a well-known structured file format (JSON, YAML, XML, or whatever) that
can be read without linking against GHC.
I agree that the strictness there was surprising, but I think this may be a
case where what is superficially expected is, in the end, inconsistent.
What about:
let ~(!x, !y) = undefined in ()
If nested bang patterns implied strictness of their parents, this valid
expression seems not to make
gt;
>
> *From:* ghc-devs *On Behalf Of *Chris Smith
> *Sent:* 14 June 2020 14:43
> *To:* ghc-devs@haskell.org
> *Subject:* Looking for a recent error reporting change
>
>
>
> Hi. In GHC 8.6.5, if I compile a main module that both fails to define
> `main` and also contains ot
Hi. In GHC 8.6.5, if I compile a main module that both fails to define
`main` and also contains other errors, the other errors are not reported
because GHC aborts after realizing that there is no `main`. In GHC 8.10.1,
all errors are reported. I'm looking for where this change was made, in
the
14 matches
Mail list logo