caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Gabriel Kerneis <gabriel@kerneis.info>
To: oleg@okmij.org
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] ANN: improved BER MetaOCaml N101, for OCaml 4.01
Date: Thu, 28 Nov 2013 09:48:59 +0000	[thread overview]
Message-ID: <20131128094859.GB4052@kerneis.info> (raw)
In-Reply-To: <20131127073030.28963.qmail@www1.g3.pair.com>

Hi Oleg,

On Wed, Nov 27, 2013 at 07:30:30AM -0000, oleg@okmij.org wrote:
> The scope extrusion check first introduced in BER N100 made it
> possible to remove environment classifiers while still preserving the
> static guarantee: if the generator finishes successfully, the
> generated code is well-typed and well-scoped. Environment classifiers
> ensured well-scopedness when type-checking the generator -- but only
> for pure generators. The scope extrusion check is executed when the
> generator is run; however the check is comprehensive. Scope extrusion
> is always caught, and caught early, whether the generator is effectful
> or not.

I'm not sure I understand correctly the difference between open and close code,
and what is the challenge with effects.  Could you please give examples of:
(1) a pure generator for well-typed, well-scoped open code,
(2) a pure generator for well-typed, ill-scoped open code,
(3) an effectful generator for well-typed, ill-scoped open code.

I assume (2) would be caught statically by BER N100, and (3) dynamically by BER
N101. But what would happen for (2) with BER N100?

Many thanks,
-- 
Gabriel

  parent reply	other threads:[~2013-11-28  9:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-27  7:30 oleg
2013-11-27 12:45 ` Ömer Sinan Ağacan
2013-11-27 13:33   ` rixed
2013-11-28  9:48 ` Gabriel Kerneis [this message]
2013-11-28 11:15   ` oleg

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=20131128094859.GB4052@kerneis.info \
    --to=gabriel@kerneis.info \
    --cc=caml-list@inria.fr \
    --cc=oleg@okmij.org \
    /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 NNTP newsgroup(s).