Hi Simon,
this doesn't look like a problem with the testsuite driver. The testsuite
driver indeed calls 'diff', but has been doing so for years. Nothing
changed there. I just ran the testsuite on Windows with msys2 to double
check, and didn't get any framework errors either.
Something changed in
2015-06-08 23:19 GMT+02:00 Austin Seipp aus...@well-typed.com:
Sigh. I'll revert this. I couldn't reproduce this on my two machines,
but I should have figured it would have broken something. I took a
chance. :)
So the documentation builds fine for you? I believed the FreeBSD
builders failed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello *,
the subject says it all. After we successfully put `=`
into Monad, it is time to remove something in return: `fail`.
Like with the AMP, I wrote up the proposal in Markdown
format on Github, which you can find below as a URL, and in
verbatim
On 2015-06-09 at 22:43:30 +0200, David Luposchainsky wrote:
[...]
https://github.com/quchen/articles/blob/master/monad_fail.md
Here's a short abstract:
- Move `fail` from `Monad` into a new class `MonadFail`.
[...]
+1 obviously :-)
___
ghc-devs
David Luposchainsky dluposchain...@googlemail.com writes:
the subject says it all. After we successfully put `=`
into Monad, it is time to remove something in return: `fail`.
+1
John
___
ghc-devs mailing list
ghc-devs@haskell.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10.06.2015 00:26, Johan Tibell wrote:
As a consequence, in current Haskell, you can not use Monad-polymorphic code
safely, because although it claims to work for all Monads, it might just crash
on you. This kind of implicit non-totality baked
Thanks for putting this together.
The proposal says:
As a consequence, in current Haskell, you can not use Monad-polymorphic
code safely, because although it claims to work for all Monads, it might
just crash on you. This kind of implicit non-totality baked into the class
is terrible.
Is this
+1 from me for both the spirit and the substance of this proposal. We've
been talking about this in the abstract for a while now (since ICFP 2013 or
so) and as concrete plans go, this strikes me as straightforward and
implementable.
-Edward
On Tue, Jun 9, 2015 at 10:43 PM, David Luposchainsky
Yes, please try the patch here - I think it should fix it (it carries
an explanation too): https://phabricator.haskell.org/D970
On Tue, Jun 9, 2015 at 2:10 AM, Páli Gábor János pali.ga...@gmail.com wrote:
2015-06-08 23:19 GMT+02:00 Austin Seipp aus...@well-typed.com:
Sigh. I'll revert this. I
I uninstalled, reinstalled , did a cabal install of haddock then ghc-core
and threadscope and saw no errors so I guess we are fine as long as the
next version includes the latest haddock. I notice on the 7.10.2 active
tickets page there is a ticket saying that 7.10.2 needs the latest haddock.
On
I can give a couple of rather academic issues that the status quo causes:
An example of where this has bit us in the hindquarters in the past is that
the old Error class based instance for Monad (Either a) from the mtl
incurred a constraint on the entire Monad instance in order to support
'fail'.
When you did the cabal install of haddock, which haddock did you get? Isn't
2.16.0 the latest? And that should be what is in the Platform.
I guess I should check that the haddock in GHC is actually 2.16.0!
___
ghc-devs mailing list
i'll add my token +1 to the land slide
On Tue, Jun 9, 2015 at 11:19 PM, Bardur Arantsson s...@scientician.net
wrote:
On 06/09/2015 10:43 PM, David Luposchainsky wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
+1
___
Libraries mailing
13 matches
Mail list logo
