Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Iris
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Model registry
Operate
Terraform modules
Monitor
Service Desk
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
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Pierre Roux
Iris
Commits
6385b7ea
Verified
Commit
6385b7ea
authored
5 years ago
by
Tej Chajed
Browse files
Options
Downloads
Patches
Plain Diff
[doc] Copy edit the heap lang documentation
parent
8ada8daa
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/heap_lang.md
+3
-3
3 additions, 3 deletions
docs/heap_lang.md
with
3 additions
and
3 deletions
docs/heap_lang.md
+
3
−
3
View file @
6385b7ea
...
...
@@ -76,8 +76,8 @@ Tactics for the heap:
-
`wp_alloc l as "H"`
: Reduce an allocation instruction and call the new
location
`l`
(in the Coq context) and the points-to assertion
`H`
(in the
spatial context). You can leave
away
the
`as "H"`
to introduce it as an
anonymous assertion,
i.e., that
is equivalent to
`as "?"`
.
spatial context). You can leave
out
the
`as "H"`
to introduce it as an
anonymous assertion,
which
is equivalent to
`as "?"`
.
-
`wp_load`
: Reduce a load operation. This automatically finds the points-to
assertion in the spatial context, and fails if it cannot be found.
-
`wp_store`
: Reduce a store operation. This automatically finds the points-to
...
...
@@ -126,7 +126,7 @@ value lambda). However, the *specification* for parallel composition should use
value lambdas, because prior to applying it the term will be reduced as much as
possible to achieve a normal form. To facilitate this, we define a copy of the
`e1 ||| e2`
notation in the value scope that uses value lambdas.
This is not actually a value, but we still
b
ut it in the value scope to
This is not actually a value, but we still
p
ut it in the value scope to
differentiate from the other notation that uses expression lambdas. (In the
future, we might decide to add a separate scope for this.) Then, we write the
canonical specification using the notation in the value scope.
...
...
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