On 11/06/2013, at 1:58 AM, Alberto G. Corona wrote:
> I have ever wondered how a committee could have made Haskell.
A committee made Algol 60, described as "an improvement on most
of its successors". A committee maintains Scheme.
On the other hand, an individual gave us Perl.
And an individual
Richard Eisenberg wrote:
> without ScopedTypeVariables, the n that you would put on your annotation
> is totally unrelated to the n in the instance header, but this is benign
> becau
> se GHC can infer the type anyway. With ScopedTypeVariables, the `n`s are
> the same, which luckily agrees with
Yes I'm really hoping Zurihac is on the weekend so I can actually come :) :)
G
On Mon, Jun 10, 2013 at 9:36 PM, Bas van Dijk wrote:
> On 10 June 2013 19:38, Roman Cheplyaka wrote:
> > Hi Bas,
> >
> >> When: Thursday 30 August - Friday 1 September
> >> Where: Erudify offices, Zurich, Switzerl
On 10 June 2013 19:38, Roman Cheplyaka wrote:
> Hi Bas,
>
>> When: Thursday 30 August - Friday 1 September
>> Where: Erudify offices, Zurich, Switzerland
>
> Is this a mistake? 30 August is Friday, 1 September is Sunday.
Oops! You're right, that's embarrassing :-)
Thanks,
Bas
==
CALL FOR PAPERS
WGP 2013
9th ACM SIGPLAN Workshop on Generic Programming
Boston, Massachusetts, USA
Saturday,
I have ever wondered how a committee could have made Haskell.
My conclusion is the following:
For one side there were many mathematicians involved, the authors of the
most terse language(s) existent: the math notation.
For the other, the lemma "avoid success at all costs" which kept the
committ
On Mon, Jun 10, 2013 at 05:44:26PM +0400, MigMit wrote:
> It really sounds rude, to demand promises from somebody who just gave you a
> big present.
Without wishing to preempt Zed Becker, I interpreted his email as an
expression of delight at how well Haskell has been designed and of hope that
it
It really sounds rude, to demand promises from somebody who just gave you a big
present.
Отправлено с iPhone
10.06.2013, в 16:11, Zed Becker написал(а):
> Hi all,
>
> Haskell, is arguably the best example of a design-by-committee language. The
> syntax is clean and most importantly, consiste
On Mon, Jun 10, 2013 at 03:21:28PM +0200, Ertugrul Söylemez wrote:
> Tom Ellis wrote:
> > Hear hear! Hopefully we, the Haskell community, will be able to
> > support this endevour with our time and efforts.
>
> Every Haskell user does this in their own way by use, feedback, uploads
> to Hackage,
Tom Ellis wrote:
> Hear hear! Hopefully we, the Haskell community, will be able to
> support this endevour with our time and efforts.
Every Haskell user does this in their own way by use, feedback, uploads
to Hackage, authoring wiki articles or blog articles or simply by
helping people. The Ha
It's definitely hashable. Here's a minimal failing test case:
https://gist.github.com/gregorycollins/5748445
On Sat, May 18, 2013 at 11:38 PM, Roman Cheplyaka wrote:
> Indeed it looks like a bug in hashable — it goes away with
> hashable-1.1.2.5.
>
> Building with -f-sse2 results in a linker er
Hm...
Haskell was /developed/ by teams, but we had BEFORE: hope, miranda, ML
... The heritage is quite important.
And individuals (say, Mark Jones) contributed to Haskell constructs. So,
the /design/ is not entirely "committe based"
1.
Promise to me, and the
Zed,
while I don't disagree regarding the clean and consistent syntax of
Haskell, do you realize that some people would argue that camels are horses
designed by committee too? :)
While designing by committee guarantees agreement across a large number of
people, it does not always ensure efficienc
On Mon, Jun 10, 2013 at 05:41:05PM +0530, Zed Becker wrote:
> Haskell, is arguably the best example of a design-by-committee language.
> The syntax is clean and most importantly, consistent. The essence of a
> purely functional programming is maintained, without disturbing its real
> world capacit
On Mon, Jun 10, 2013 at 05:41:05PM +0530, Zed Becker wrote:
>
> Haskell, is arguably the best example of a design-by-committee language.
You do realize that "design-by-committee" is generally understood to
refer to the antipattern where a committee discusses a design to death
and delivers an inc
Hi all,
Haskell, is arguably the best example of a design-by-committee language.
The syntax is clean and most importantly, consistent. The essence of a
purely functional programming is maintained, without disturbing its real
world capacity.
To all the people who revise the Haskell standard, a
16 matches
Mail list logo