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
3d049510
Commit
3d049510
authored
Oct 14, 2020
by
Mickael Laurent
Browse files
some reflexions...
parent
6f988c52
Changes
1
Hide whitespace changes
Inline
Side-by-side
new_system.tex
View file @
3d049510
...
...
@@ -16,6 +16,11 @@
\end{array}
\end{equation}
TODO: the then and else expressions of typecases have no associated variable,
altough the env refinement rules could refine their types...
Is this an issue? Should we require an atomic in the then and else branchs
(seems difficult: there would be no equivalent normal form)?
TODO: Which restrictions on types? (cannot test a precise arrow type, etc)
\subsection
{
Typing rules
}
...
...
@@ -165,11 +170,10 @@ TODO: Algorithmic rules
\end{mathpar}
TODO: example: application
$
x y
$
with
$
x
$
an union of arrow. Candidates
of a variable with a function type should be all the union of arrows of its type?
\\
More generally, a variable that can be written only has an union should be splitted
along this union. Otherwise,
$
\letexp
{
x
}{
\cdots
}{
x
}$
will never be splitted. Or better:
there should be a special split that means "all splits" (it will also be useful when
we will add polymorphism).
for
$
x
$
should be all the different union of arrows of its type?
TODO: Candidates for a variable should be a special "all splits".
Otherwise,
$
\letexp
{
x
}{
\cdots
}{
x
}$
will never be splitted.
TODO: test type system with
$
\lambda
x:
\pair
{
\Int
}{
\Int
}
\lor\pair
{
\Bool
}{
\Bool
}
.
(
\pi
_
1
x,
\pi
_
2
x
)
$
...
...
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