Skip to content
GitLab
Menu
Projects
Groups
Snippets
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
Menu
Open sidebar
Giuseppe Castagna
occurrence-typing
Commits
ff6fde19
Commit
ff6fde19
authored
Feb 28, 2020
by
Kim Nguyễn
Browse files
typos.
parent
819cb296
Changes
2
Show whitespace changes
Inline
Side-by-side
extensions.tex
View file @
ff6fde19
...
...
@@ -14,7 +14,7 @@ extend our work to records. Although we use the record types as they are
defined in CDuce we cannot do the same for CDuce record expressions
which require non-trivial modifications for occurrence typing,
especially because we want to capture record field extension and field
deletion which current radual typing systems fail to capture. CDuce record types are obtained by extending types with the
deletion which current
g
radual typing systems fail to capture. CDuce record types are obtained by extending types with the
following two type constructors:
\\
[1.4mm]
%
\centerline
{\(
\textbf
{
Types
}
~~ t ~ ::
=
~
\record
{
\ell
_
1
=
t
\ldots
\ell
_
n
=
t
}{
t
}
\alt
\Undef
\)}
\\
[1.4mm]
...
...
language.tex
View file @
ff6fde19
...
...
@@ -71,7 +71,7 @@ for $j=1,2$. In~\eqref{expressions}, $c$ ranges over constants
(e.g.,
\texttt
{
true
}
,
\texttt
{
false
}
,
\texttt
{
1
}
,
\texttt
{
2
}
,
...) which are values of basic types (we use
$
\basic
{
c
}$
to denote the
basic type of the constant
$
c
$
);
$
x
$
ranges over variables;
$
(
e,e
)
$
denote pairs and
$
\pi
_
i e
$
their projections;
$
\tcase
{
e
}{
t
}{
e
_
1
}{
e
_
2
}$
denote
s
pairs and
$
\pi
_
i e
$
their projections;
$
\tcase
{
e
}{
t
}{
e
_
1
}{
e
_
2
}$
denotes the type-case expression that evaluates either
$
e
_
1
$
or
$
e
_
2
$
according to whether the value returned by
$
e
$
(if any) is of type
$
t
$
or not;
$
\lambda
^{
\wedge
_{
i
\in
I
}
s
_
i
\to
t
_
i
}
x.e
$
is a value of type
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment