This scheme is ideal for companies that make
significant use of Haskell and wish to fund specific projects.
Additionally, there are new associate and academic membership options.
These enable companies and academic groups to support the general health
of the Haskell development platform, but w
Original-Via: uk.ac.nsf; Thu, 28 Nov 91 00:35:19 GMT
Personally, I think n+k patterns are a baroque left-over from views that
someone thought would be nice to retain when views were abandonned. They
should either be thrown out or generalised in a more regular way.
Let's throw them out.
Original-Via: uk.ac.st-and.cs; Wed, 27 Nov 91 11:41:37 GMT
Mark Jones sent me a message which included this:
-- PS. While I'm writing to you, can I ask about your other examples for
-- using c*n+k patterns? I like the examples you gave, but can't think of
-- too many other applications. If y
Original-Via: uk.ac.nsf; Sat, 16 Nov 91 09:47:52 GMT
The operator which was called `in` in version 1.0 seems to have
vanished without trace since `in` became a reservedid. Can I suggest
it be restored to PreludeList, possibly with the name `contains`:
contains ::
#
X-Comment5: #
> From: Tony Davie <[EMAIL PROTECTED]>
> Date: Wed, 13 Nov 91 16:58:03 GMT
> To: haskell
> Subject: membership
>
> The operator which was called `in` in version 1.0 seems to have
> vanished wi
Original-Via: uk.ac.st-and.cs; Wed, 13 Nov 91 16:58:45 GMT
The operator which was called `in` in version 1.0 seems to have
vanished without trace since `in` became a reservedid. Can I suggest
it be restored to PreludeList, possibly with the name `contains`:
contains :: (Eq a) => [a] -> a -> Bool
