Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
sgdt
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
gradual-typing
sgdt
Commits
d116a549
Commit
d116a549
authored
6 years ago
by
Max New
Browse files
Options
Downloads
Patches
Plain Diff
laziness tweak, typo
parent
aa8135d7
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
paper/gtt.tex
+4
-3
4 additions, 3 deletions
paper/gtt.tex
with
4 additions
and
3 deletions
paper/gtt.tex
+
4
−
3
View file @
d116a549
...
...
@@ -4508,7 +4508,7 @@ The following lemma shows this forms a computation ep pair:
From this, we see that the easiest way to construct an interpretation
of the dynamic computation type is to make it a lazy product of all
the ground types
$
\u
G
$
:
$
\dyn
s
\cong
\With
_{
\u
G
}
\u
G
$
.
the ground types
$
\u
G
$
:
$
\dyn
c
\cong
\With
_{
\u
G
}
\u
G
$
.
Using recursive types, we can easily make this a definition of the
interpretations:
...
...
@@ -9383,8 +9383,9 @@ Finally note that once we have introduced the extra thunks to model
difference between call-by-name and call-by-need is only relevant for
performance reasons.
%
Therefore the resulting cast semantics we produce should also be
valid for call-by-need evaluation.
Since divergence and uncatchable errors are idempotent, and these are
usually the only effects in lazy languages, the resulting cast
semantics GTT produces should also be valid for call-by-need.
\citet
{
Degen2012TheIO
}
give an analysis of different cast semantics
for contracts in lazy languages, specifically based on Haskell, so
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment