rivial problems. The switch in Control.Exception (from data
Exception to class Exception) was much more disrupting, adapting programs
meant lots of changes everywhere exceptions are handled, not just adding
some trivial instances. Still people managed the transition.
Cheers
--
Ben Franksen
rs to, since in both of the
hierarchies you linked to Applicative *is* a super class of Monad.
Cheers
> On 25/10/12 04:49, Ben Franksen wrote:
>> First, let me make it clear that nowadays we are of course (I hope!)
talking
>> about making not only Functor, but Applicative a super-
e package to all builds.
BTW, I think this could be a general method to "backward fix" compatibility
problems when re-organising core libraries.
And one last caveat: Cabal itself would need to exercise some restraint
w.r.t. using new language or library features, since it must be buildab
ration.
Cheers
--
Ben Franksen
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachm€nts
___
Haskell-prime mailing list
Haskell-prime@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-prime
Hi Everyone
On Wednesday, December 04, 2013 09:19:48 Brandon Allbery wrote:
> The functionality is similar but different, insofar as Windows
still
> has legacy drive paths and the current directory is maintained
> separately for each one; I would expect this to be exposed in a
> Windows version.
Am 06.10.2018 um 05:18 schrieb Anthony Clayden:
> On Sat, 6 Oct 2018 at 9:47 AM, Petr Pudlák wrote:
> such as the important laws between `return` and `>>=`. And then for example
>> a class with just `return` doesn't give any information what `return x`
>> means or what should be its properties.
>>
Am 08.10.2018 um 11:21 schrieb Anthony Clayden:
> I wonder how different would have been the history of Haskell if Wadler had
> not borrowed the terminology "class" and "method". Since Helium has a focus
> on Haskell learners/beginners: I wonder how much confusion we might have
> saved those coming
