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
06147cce
Commit
06147cce
authored
6 years ago
by
Dan Licata
Browse files
Options
Downloads
Patches
Plain Diff
spell check response
parent
e3a2cdee
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
popl19/response2.md
+2
-2
2 additions, 2 deletions
popl19/response2.md
with
2 additions
and
2 deletions
popl19/response2.md
+
2
−
2
View file @
06147cce
...
...
@@ -16,7 +16,7 @@ refactorings and optimizations. For instance, upcasts, as complex
values, can be freely (de)-duplicated, discarded if not used, and lifted
out of loops as if they were values. Downcasts, as complex stacks, are
strict in their input, which aids strictness analysis, as in optimizers
for lazy lang
a
uges.
for lazy langu
a
ges.
2.
**Reviewer C**
asks (Question1) about the meaning of L514 and whether or not
our syntactic theory of term dynamism and equivalence is not only sound
...
...
@@ -86,7 +86,7 @@ to values or non-effectful code).
optimization, it's the other direction that fails for these cases right?"
Yes, in the eager cast semantics, the eta law for functions should be
an ordering
`V <= \x -> V x`
but it's debat
e
able whether this means that
an ordering
`V <= \x -> V x`
but it's debatable whether this means that
the right should be allowed to be optimized to the left. This would make
the semantics of the program dependent on the precise behavior of the
optimizer, so it would be very hard to change the optimizer without
...
...
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