unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Some guile-unify activities
Date: Mon, 09 May 2011 14:42:58 +0200	[thread overview]
Message-ID: <m3tyd459kd.fsf@unquote.localdomain> (raw)
In-Reply-To: <BANLkTinhsy7iNVA5GEH5YQ5L_6UsiLSoVg@mail.gmail.com> (Stefan Israelsson Tampe's message of "Mon, 9 May 2011 13:15:10 +0200")

On Mon 09 May 2011 13:15, Stefan Israelsson Tampe <stefan.itampe@gmail.com> writes:

> Hmm, type annotations in typed racket is defined according to
>
> http://docs.racket-lang.org/ts-guide/more.html#%28part._.Type_.Annotation_and_.Binding_.Forms%29
>
> Any objections against that scheme? ideas?

I think that what I'm primarily interested in is a way to annotate
tree-il with type information, which the compiler may use to generate
more efficient code.  However I think it's premature to bless a
particular encoding of that information in Scheme, or any particular
type system... basically it should be a field in the tree-il, I think,
and anything else can be built on top of that.

MHO anyway :)  But yes, there is a lot to learn from Racket about this.
They've done the most advanced work that I'm aware of.

Andy
-- 
http://wingolog.org/



  reply	other threads:[~2011-05-09 12:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-06 21:18 Some guile-unify activities Stefan Israelsson Tampe
2011-05-06 21:26 ` Noah Lavine
2011-05-08 15:38 ` Ludovic Courtès
2011-05-08 15:52 ` Andy Wingo
2011-05-09 11:15   ` Stefan Israelsson Tampe
2011-05-09 12:42     ` Andy Wingo [this message]
2011-05-09 18:35       ` Stefan Israelsson Tampe
2011-05-09 21:46         ` Andy Wingo
2011-05-10  9:00           ` Stefan Israelsson Tampe
2011-05-10  9:15             ` 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=m3tyd459kd.fsf@unquote.localdomain \
    --to=wingo@pobox.com \
    --cc=guile-devel@gnu.org \
    --cc=stefan.itampe@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).