From: Andy Wingo <wingo@pobox.com>
To: Noah Lavine <noah.b.lavine@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: The progress of hacking guile and prolog
Date: Fri, 26 Nov 2010 11:45:02 +0100 [thread overview]
Message-ID: <m3r5e8z7m9.fsf@unquote.localdomain> (raw)
In-Reply-To: <AANLkTi=6irK6naatSmcDBEs+wNQvOYXTikX5CAc5kq7O@mail.gmail.com> (Noah Lavine's message of "Tue, 23 Nov 2010 20:54:37 -0500")
Hi Noah,
On Wed 24 Nov 2010 02:54, Noah Lavine <noah.b.lavine@gmail.com> writes:
> What I'm thinking of is like racket contracts, but with the idea of
> "trusted modules", which might involve static checking.
Yeah, definitely. Like the interface between typed and untyped code in
racket, also. I don't know very much about the relationship between
types and contracts, though.
> I'm curious in general though whether it would be possible and
> worthwhile to statically check programmer-defined ideas, as long as
> the interface is easy enough to use. For instance, what if you could
> ask Guile to check that your tree structure always remained a binary
> tree? Or better, what if you wrote a GUI program and checked that the
> callbacks you passed to the GUI library would always return? (I know
> it's not possible in general, but I think it will work for a subset of
> procedures that will include some interesting ones.)
It's certainly interesting! As I understand things (which is not very
far), Racket allows for this via other "languages". Guile could do that
too. We might need some more generic support for this kind of thing in
the compiler infrastructure or in tree-il or whatever, but I would like
to make it possible to experiment with these linguistic ideas, with the
kind of isolation provided by modules.
Cheers,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2010-11-26 10:45 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 20:23 The progress of hacking guile and prolog Stefan Israelsson Tampe
2010-11-03 23:43 ` Ludovic Courtès
2010-11-04 2:40 ` Noah Lavine
2010-11-10 17:55 ` Stefan Israelsson Tampe
2010-11-11 19:10 ` Noah Lavine
2010-11-11 16:26 ` Ludovic Courtès
2010-11-11 19:13 ` Noah Lavine
2010-11-11 19:15 ` Noah Lavine
2010-11-15 23:10 ` Typechecking I Stefan Israelsson Tampe
2010-11-20 11:46 ` Andy Wingo
2010-11-20 11:25 ` The progress of hacking guile and prolog Andy Wingo
2010-11-24 1:54 ` Noah Lavine
2010-11-24 16:45 ` Stefan Israelsson Tampe
2010-11-24 18:00 ` piper schemigan Stefan Israelsson Tampe
2010-11-24 20:18 ` Andreas Rottmann
2010-11-25 21:17 ` Ludovic Courtès
2010-11-26 22:18 ` Stefan Israelsson Tampe
2010-11-28 22:30 ` Guile-SCSH Ludovic Courtès
2010-11-28 23:02 ` Guile-SCSH Stefan Israelsson Tampe
2010-11-28 23:24 ` Guile-SCSH Jose A. Ortega Ruiz
2010-11-29 18:56 ` Guile-SCSH Stefan Israelsson Tampe
2010-11-29 21:26 ` http://gitorious.org/guile-scsh/guile-scsh Stefan Israelsson Tampe
2010-11-30 23:21 ` Guile-Facade Ludovic Courtès
2010-11-25 21:26 ` The progress of hacking guile and prolog Ludovic Courtès
2010-11-26 16:41 ` Noah Lavine
2010-11-26 10:45 ` Andy Wingo [this message]
2010-11-20 11:26 ` Andy Wingo
2010-11-04 17:57 ` Stefan Israelsson Tampe
2010-11-05 21:19 ` Stefan Israelsson Tampe
2010-11-19 23:11 ` GLIL->C compilation Ludovic Courtès
2010-11-19 23:20 ` Stefan Israelsson Tampe
2010-11-19 23:56 ` Ludovic Courtès
2010-11-20 12:18 ` Andy Wingo
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3r5e8z7m9.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=noah.b.lavine@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).