From: Jacques Carette <carette@mcmaster.ca>
To: Jon Harrop <jon@ffconsultancy.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Patterns that evaluate
Date: Wed, 14 Feb 2007 16:33:05 -0500 [thread overview]
Message-ID: <45D38011.2040907@mcmaster.ca> (raw)
In-Reply-To: <200702142105.48663.jon@ffconsultancy.com>
[Many excellent ideas on Active Patterns removed]
Jon Harrop wrote:
> That could be written much more elegantly, something like this:
>
> let rec rewrite rule = function
> | Int _ | Var _ as f -> rule f
> | Add(f, g) -> Add(rewrite rule f, rewrite rule g)
> | Mul(f, g) -> Mul(rewrite rule f, rewrite rule g)
>
Following ideas of Barry Jay, this could be even more simply written as
let rec rewrite rule = function
| u _ as f -> rule f
| b(f, g) -> b(rewrite rule f, rewrite rule g)
where u and b are supposed to be bound (to respectively unary and binary
constructors).
Yes, the 'type' of the function rewrite needs higher-order polymorphism
(or polytypism or ...) to work. See Tim Sheard's Omega for one rather
nice way to do that.
Jacques
next prev parent reply other threads:[~2007-02-14 21:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-13 22:04 Jacques Carette
2007-02-13 22:07 ` [Caml-list] " Jon Harrop
2007-02-14 0:10 ` Jacques Carette
2007-02-14 18:20 ` Edgar Friendly
2007-02-14 18:55 ` Gerd Stolpmann
2007-02-14 19:10 ` Denis Bueno
2007-02-14 19:11 ` Jacques Carette
2007-02-14 19:25 ` Gerd Stolpmann
2007-02-14 20:30 ` Edgar Friendly
2007-02-14 21:05 ` Jon Harrop
2007-02-14 21:33 ` Jacques Carette [this message]
2007-02-14 22:34 ` Martin Jambon
2007-02-15 0:26 ` Jacques Garrigue
2007-02-15 3:57 ` Jon Harrop
2007-02-15 22:43 ` Don Syme
2007-02-14 20:29 ` Nathaniel Gray
2007-02-14 21:10 ` Jacques Carette
2007-02-15 3:53 ` skaller
2007-02-15 13:41 ` Jacques Carette
2007-02-15 14:10 ` skaller
2007-02-15 20:43 ` Nathaniel Gray
2007-03-07 11:15 ` Oliver Bandel
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=45D38011.2040907@mcmaster.ca \
--to=carette@mcmaster.ca \
--cc=caml-list@inria.fr \
--cc=jon@ffconsultancy.com \
/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