Hi, everyone. Long time no see. I have a specific proposal for scoped type
variables, which is totally different from plans A and B, and which I'd like
people to pick to pieces for me. (Especially you, Simon.)
Type variable scoping in System F is simple: the type bindings are explicit
and follow
| just one more problem is that this issue is too complicated. i'm not
| sure that i correctly understands details, but for me the situation
| seems like this: in 6.4 it was no distinction between declarations and
| usages of type variables - first use declared it, while in 6.6 we have
| exactly
This message is about scoped type variables. I'm sending it to the Haskell
mailing list, because I think that the question of scoped type variables is of
general interest to Haskellers, but I suggest that you all send *replies* to
Haskell Café, where this thread originated.
Simon
The
Hello Simon,
Wednesday, October 18, 2006, 12:09:40 PM, you wrote:
Other alternatives would be: do something about partial type
signatures; or make GADT type inference more sophisticated (and
thereby perhaps less predicatable).
just one more problem is that this issue is too complicated. i'm
Hi,
let me answer your questions by comparing what's implemented in Chameleon.
(For details see
http://www.comp.nus.edu.sg/~sulzmann/chameleon/download/haskell.html#scoped)
QUESTION 1 -
In short, I'm considering adopting the Mondrian/Chameleon rule for GHC.
There are two
| This is a great example, thanks for posting it. However, I feel like
| the real problem in this example is the lexically-scoped type
| variables declared with your function f.
Paul's message gives me an excuse to consult the Haskell list about the
design of lexically scoped type variables. I
-Jones
Sent: den 25 november 2004 11:44
To: [EMAIL PROTECTED]
Subject: [Haskell] Lexically scoped type variables
| This is a great example, thanks for posting it. However, I feel like
| the real problem in this example is the lexically-scoped type
| variables declared with your function f
