gasche

(*pp camlp4orf *)

(* ty_enum_to_int : Camlp4 (3.10) Syntax extension
    type test = | A | B | C | D with to_int 
translates to :
   type test = | A | B | C | D
   let test_to_int = function | A -> 0 | B -> 1 | C -> 2 | D -> 3
   let test_of_int = function | 0 -> A | 1 -> B | 2 -> C | 3 -> D

Compilation command :

gasche

Need: we want the opam file commited in the opam-repository to be
formatted such that programmatically parsing and re-printing them is
a no-op. Today we don't have this, and this means that bulk script
changes to the opam-repository metadata creates much larger diff than
necessary.

In fact, we propose to install many different scripts named
  opam-fmt-$OPAMVERSION
with each script depending on the corresponding version of opam-lib.

gasche

Keybase proof

I hereby claim:

• I am gasche on github.
• I am gasche (https://keybase.io/gasche) on keybase.
• I have a public key ASBWH5G2wwTWgO9Sh8Fj0D_ZTvvaYqTR3vRCIbkkrXFLuQo

To claim this, I am signing this object:

gasche

We thank the reviewers for their work on our article and their
detailed feedback.

We wish to first address the two main points raised by the reviewers:

A. The (informal and technical) meaning of the main result, the Full
   Abstraction theorem for the embedding of U into UL.

B. The choice of paper structure given the page limits (and in
   particular the question of what presentation would make sense in

gasche

We thank the reviewers for their work on our submission and their
thoughtful comments. Our response is in two parts: discussion of
high-level questions, then more reviewer-specific comments. The
document is designed to have the most important points first, so that
you can stop reading at any point.

# High-level questions

First, we note why we think it would be nice to see this paper at
FSCD.

gasche

We thank the reviewers for their work on our submission and their thoughtful comments. Our response is in two parts: discussion of high-level questions, then more reviewer-specific comments. The document is designed to have the most important points first, so that you can stop reading at any point.

High-level questions

First, we note why we think it would be nice to see this paper at FSCD.

gasche

We thank the reviewers for their work on our submission and their thoughtful comments. Our response is in two parts: discussion of high-level questions, then more reviewer-specific comments. The document is designed to have the most important points first, so that you can stop reading at any point.

High-level questions

First, we note why we think it would be nice to see this paper at FSCD.

gasche

We thank the reviewers for their work on our submission and their thoughtful comments. Our response is in two parts: discussion of high-level questions, then more reviewer-specific comments. The document is designed to have the most important points first, so that you can stop reading at any point.

High-level questions

First, we note why we think it would be nice to see this paper at FSCD.