From: John Max Skaller <skaller@ozemail.com.au>
To: caml-list@inria.fr
Subject: [Caml-list] fixpoint
Date: Sun, 04 Aug 2002 06:03:23 +1000 [thread overview]
Message-ID: <3D4C370B.1050201@ozemail.com.au> (raw)
Excuse dumb question about lambda calculus.
I'm using a typed lambda calculus for a kinding system
(the types are TYPE, TYPE->TYPE etc).
I'm uncertain how to handle recursion though.
Example:
list a = 1 + a * list a
or
list = fix f . fun a. 1 + a * f a
now we need:
list int = 1 + int * list int
or
list int = fix x . 1 + int * x
which suggests the following reduction:
fix f . fun x . e ==> fix z . e [f x -> z]
Well, the rule works in this case. Will it always work?
--
John Max Skaller, mailto:skaller@ozemail.com.au
snail:10/1 Toxteth Rd, Glebe, NSW 2037, Australia.
voice:61-2-9660-0850
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next reply other threads:[~2002-08-03 20:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-03 20:03 John Max Skaller [this message]
2002-08-04 5:04 ` John Max Skaller
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=3D4C370B.1050201@ozemail.com.au \
--to=skaller@ozemail.com.au \
--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