In my limited experience thus far, it seems to me that a substantial
majority of modules that start out needing one of these end up needing the
other one too. They appear to be two sides of the same coin, each allowing
for (slightly) more powerful termination checking. Should the two just be
made
On 2015-02-06 at 07:05:35 +0100, David Feuer wrote:
In my limited experience thus far, it seems to me that a substantial
majority of modules that start out needing one of these end up needing the
other one too. They appear to be two sides of the same coin, each allowing
for (slightly) more
Named wildcards follow the scoping behaviour of ScopedTypeVariables but
without the forall. See the following example:
{-# LANGUAGE PartialTypeSignatures, NamedWildCards #-}
{-# OPTIONS_GHC -fno-warn-partial-type-signatures #-}
module Scope where
f :: _a - _b - _a
f x y = x :: _b
I really don't
Peter,
OK. This is really beyond my knowledge. Might you and Simon be able to work
out something together? I can advise on FloatOut if necessary.
Simon
| -Original Message-
| From: Peter Wortmann [mailto:sc...@leeds.ac.uk]
| Sent: 05 February 2015 11:47
| To: Simon Peyton Jones;
Simon,
2015-02-05 17:44 GMT+01:00 Simon Peyton Jones simo...@microsoft.com:
3. It interferes with generalisation.
For (3), consider
let f :: _a - _a
f xs = reverse xs
in (f True, f ‘x’)
Here, f gets the type f :: forall b. [b] - [b], and _a is unifed with [b].
