Good catch. Adding and subtracting over and over relying on massive
cancellation over and over is a recipe for floating point disaster!
That said, so is adding small things to a large thing over and over, you'll
accumulate the rounding error from the addition of small numbers to the
large base.
Hi,
I created a stub Backpack entry in the Haskell wiki using the abstract of the
paper.
Howard
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Hello friends,
I'm hoping to land Backpack (the patch is two years in the making now!)
for GHC 8.2, even though 8.2 is intended to be a stabilization and
performance release. In this email, I will make the case that the
Backpack patch is relatively self-contained and will not affect
non-Backpack
FWIW. Often when I encounter that error, I want `ScopedTypeVariables`,
yet my code doesn’t always has the scoped type variable used.
So even GHC could parse further and propose it to me, there isn’t anything from
to do it :(
I don’t know if many use /just/ `ExplicitForAll`...
- Oleg
> On 11
Hello everyone,
I am working on my first ticket (#11669, linked below)
and I have some doubts after a little bit of hacking.
There was a hint that an error message should be
changed from the one suggesting RankNTypes to ExplicitForall.
In my opinion it would be quite confusing for the user,
https://blog.rust-lang.org/2016/08/10/Shape-of-errors-to-come.html
I'd particularly note that their compiler errors were dramatically
better to begin with, now they're doing this. Thought the list would
be interested in this.
--- Chris
___
ghc-devs
Hi Simon,
> * Current specification is here: ...
It's in a Haskell wiki page: [1]. This summarizes the current proposed
syntax for -XDerivingStrategies, how GHC will choose a strategy in the
absence of an explicit strategy, and also goes over some alternative
syntaxes that have been proposed
Ryan
I've been on holiday, and there's been a lot of traffic on this
deriving-strategy thread.
Would you like to send an email summarising the state of play. Eg
* Current specification is here: ...
* Patch is here: ... (complete?)
* Unresolved issues? Ready to review?
Thanks
Simon
|
