RE: Syntax for implicit parameters
I only added 'with' because I did not want to steal *two* new keywords. One is bad enough! I proposed using 'let' (not dlet), with the '?' to distinguish dynamic from lexical bindings, but did not achieve consensus. Lack of consensus => the status quo stays. My order of preference: 1. [happy]. Use 'let' 2. [consent]. Use 'dlet' or 'with' 3. [hate] Use both 'dlet' and 'with' Would the Hugs folk be willing to adopt (2)? Simon | -----Original Message----- | From: Alastair Reid [mailto:reid@cs.utah.edu] | Sent: 18 April 2001 18:31 | To: hugs-bugs@haskell.org; glasgow-haskell-bugs@haskell.org | Subject: Syntax for implicit parameters | | | | Some months ago, there was talk about making sure GHC and Hugs use the | same syntax for implicit parameters and (most importantly) that that | syntax should not introduce the keyword "with". | | As far as I can see (from looking at both parsers and trying | examples), this discussion has not been acted on. Hugs seems to | allow: | | dlet ?x = 'a' in ?x + 1 | ?x + 1 with ?x = 'a' | | and GHC 5.0 only seems to support: | | ?x + 1 with ?x = 'a' | | Can the GHC people, the Hugs people and the implicit parameter | designers come to some sort of agreement and implement the result? | | | -- | Alastair Reid reid@cs.utah.edu http://www.cs.utah.edu/~reid/ _______________________________________________ Glasgow-haskell-bugs mailing list Glasgow-haskell-bugs@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
Simon Peyton-Jones wrote:
I only added 'with' because I did not want to steal *two* new keywords. One is bad enough! I proposed using 'let' (not dlet), with the '?' to distinguish dynamic from lexical bindings, but did not achieve consensus.
I only added `with' to GHC originally because `dlet' was essentially deprecated (although I never bothered to remove it from hugs).
Lack of consensus => the status quo stays.
My order of preference:
1. [happy]. Use 'let' 2. [consent]. Use 'dlet' or 'with' 3. [hate] Use both 'dlet' and 'with'
Would the Hugs folk be willing to adopt (2)?
That would certainly be fine by me. --Jeff
"Jeffrey R. Lewis"
Lack of consensus => the status quo stays.
My order of preference:
1. [happy]. Use 'let' 2. [consent]. Use 'dlet' or 'with' 3. [hate] Use both 'dlet' and 'with'
Would the Hugs folk be willing to adopt (2)?
That would certainly be fine by me.
What exactly does (2) imply? Does it mean we get `with' back or not? Manuel
"Manuel M. T. Chakravarty" wrote:
"Jeffrey R. Lewis"
wrote, Lack of consensus => the status quo stays.
My order of preference:
1. [happy]. Use 'let' 2. [consent]. Use 'dlet' or 'with' 3. [hate] Use both 'dlet' and 'with'
Would the Hugs folk be willing to adopt (2)?
That would certainly be fine by me.
What exactly does (2) imply? Does it mean we get `with' back or not?
I'm afraid I misspoke. I meant (2) with `with'. Sorry ;-) I'm happy to nuke `dlet'. --Jeff
"Jeffrey R. Lewis"
"Manuel M. T. Chakravarty" wrote:
"Jeffrey R. Lewis"
wrote, Lack of consensus => the status quo stays.
My order of preference:
1. [happy]. Use 'let' 2. [consent]. Use 'dlet' or 'with' 3. [hate] Use both 'dlet' and 'with'
Would the Hugs folk be willing to adopt (2)?
That would certainly be fine by me.
What exactly does (2) imply? Does it mean we get `with' back or not?
I'm afraid I misspoke. I meant (2) with `with'. Sorry ;-) I'm happy to nuke `dlet'.
The problem is that implict parameters than clash with both the HaXML and the new FFI libraries, ie, you can't use both in a module. Not nice. Manuel
Simon Peyton-Jones wrote:
[...] 1. [happy]. Use 'let' 2. [consent]. Use 'dlet' or 'with' 3. [hate] Use both 'dlet' and 'with'
Would the Hugs folk be willing to adopt (2)?
I'm getting a little bit lost in this thread: Everybody seems to agree that stealing identifiers is bad, stealing a *very* useful identifier ('with') is *very* bad, and Alastair promised to synch Hugs with GHC, so why don't we adopt (1)? Confused, Sven
participants (4)
-
Jeffrey R. Lewis -
Manuel M. T. Chakravarty -
Simon Peyton-Jones -
Sven Panne