Commit 6e33fc02 authored by Giuseppe Castagna's avatar Giuseppe Castagna
Browse files


parent 53826a2d
......@@ -3,7 +3,7 @@
\title{Description of modifications}
\title{Description of the modifications to the manuscript SCICO-S-21-00131}
......@@ -380,7 +380,7 @@ unneeded:
Why not simply present the system that's actually implemented, which
as the paper says is all that is really needed.
We added a long discussion to explain the reasons of our
choice. It is in the related work section (see: p29l ??-??) when
comparing with {[}22{]} (i.e. Tobin-Hochstadt\&Felleisen
......@@ -873,7 +873,10 @@ be useful in practice. Is there a smaller/simpler formal framework which
preserves the usefulness of these ideas?
Beppe: je ne sais pas quoi repondre
We added in the paper the reasons why we chose to study a formal
system more complex than the one that can be implemented in
practice. See also the answer to reviewer 1 at the end of
page~\pageref{complexity} of this document.
Another relevant limitation is that the basic idea of registering the
......@@ -1068,7 +1071,7 @@ languages use a mostly sound static type system, and smart-casts / type-promotio
ANYBODY? Victor?!!!
This is ground zero occurrence typing that does not require any
Kotlin and Dart is ground zero occurrence typing that does not require any
formal development. It is less expressive than a small hack that we
implemented in CDuce (which works not only when the tested
expression is a variable but also when it has a value form in which
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment