From: reig@dcs.gla.ac.uk
To: Michel.Mauny@inria.fr
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] variant with tuple arg in pattern match?
Date: Tue, 10 Apr 2001 12:47:37 +0100 (BST) [thread overview]
Message-ID: <200104101147.MAA11108@crab.dcs.gla.ac.uk> (raw)
In-Reply-To: <20010410133239.B13189@quincy.inria.fr> from "Michel Mauny" at Apr 10, 2001 01:32:39 PM
Michel Mauny wrote:
> Sure. With CamlP4's revised syntax, you would write this as
>
> type t 'a =3D
> I of int
> | B of bool
> | N of (t 'a) and (t 'a) (* parens probably unnecessary *)
> | Uncurried of int * int
>
> > Moreover, the last part (-> 'a t) is the same for all constructors and
> > can be omitted like you do in haskell (so that Xavier is happier :)
> >=20
> > type 'a t =3D
> > Int : int
> > | Bool : bool
> > | Node : 'a t -> 'a t
> > | Uncurried : int * int
>
> I'm afraid the Node case is ambiguous, here.
>
> Is the type of Node 'a t -> 'a t -> 'a t
> or is it ('a t -> 'a t) -> 'a t ?
>
> In other words, you can't know wether Node carries functions, or is
> curried.
Like in haskell, if it *looks* curried, it *is* curried.
data T a = Curried (T a) (T a)
| Function (T a -> T a)
Main> :i T
-- type constructor
data T a
-- constructors:
Curried :: T a -> T a -> T a
Function :: (T a -> T a) -> T a
Even in ocaml's current syntax, you need parens for functions in datatypes:
# type t = F of int -> int;;
Syntax error
# type t = F of (int -> int);;
type t = F of (int -> int)
Maybe other syntax of disambiguating this case are better, I'm
proposing the one I know, which seems quite regular.
Fermin Reig
-------------------
To unsubscribe, mail caml-list-request@inria.fr. Archives: http://caml.inria.fr
next prev parent reply other threads:[~2001-04-10 11:47 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-04 11:04 Chris Hecker
2001-04-04 18:47 ` Alain Frisch
2001-04-04 19:18 ` Patrick M Doane
2001-04-04 19:36 ` Chris Hecker
2001-04-04 19:49 ` Daniel de Rauglaudre
2001-04-05 8:19 ` Christian RINDERKNECHT
2001-04-04 19:49 ` Patrick M Doane
2001-04-06 13:52 ` Xavier Leroy
2001-04-07 1:42 ` Patrick M Doane
2001-04-07 6:44 ` Daniel de Rauglaudre
2001-04-07 7:42 ` Fergus Henderson
2001-04-08 19:45 ` Pierre Weis
2001-04-08 20:37 ` Charles Martin
2001-04-08 23:57 ` Brian Rogoff
2001-04-09 0:22 ` Alain Frisch
2001-04-09 16:07 ` Pierre Weis
2001-04-10 8:23 ` Michel Mauny
2001-04-10 9:14 ` Xavier Leroy
2001-04-10 10:09 ` Michel Mauny
2001-04-10 10:44 ` reig
2001-04-10 11:32 ` Michel Mauny
2001-04-10 11:47 ` reig [this message]
2001-04-10 12:10 ` reig
2001-04-10 12:35 ` Michel Mauny
2001-04-10 12:49 ` Marcin 'Qrczak' Kowalczyk
2001-04-09 6:23 ` Mattias Waldau
2001-04-09 7:34 ` Daniel de Rauglaudre
2001-04-09 15:57 ` Pierre Weis
2001-04-10 9:07 ` Sven LUTHER
2001-04-09 8:20 ` Christian RINDERKNECHT
2001-04-10 2:54 ` Patrick M Doane
2001-04-10 19:04 ` John Max Skaller
2001-04-08 0:22 jgm
2001-04-10 12:17 Dave Berry
2001-04-10 13:12 ` Marcin 'Qrczak' Kowalczyk
2001-04-10 21:26 ` Bruce Hoult
2001-04-10 22:34 ` John Prevost
2001-04-10 13:51 ` Frank Atanassow
2001-04-10 17:25 Dave Berry
2001-04-10 23:16 ` Marcin 'Qrczak' Kowalczyk
2001-04-10 17:33 Dave Berry
2001-04-10 22:34 ` John Prevost
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200104101147.MAA11108@crab.dcs.gla.ac.uk \
--to=reig@dcs.gla.ac.uk \
--cc=Michel.Mauny@inria.fr \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox