Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
I
Iris
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
116
Issues
116
List
Boards
Labels
Service Desk
Milestones
Merge Requests
20
Merge Requests
20
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Operations
Operations
Incidents
Environments
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Iris
Iris
Commits
6385b7ea
Verified
Commit
6385b7ea
authored
Dec 14, 2019
by
Tej Chajed
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
[doc] Copy edit the heap lang documentation
parent
8ada8daa
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
3 deletions
+3
-3
docs/heap_lang.md
docs/heap_lang.md
+3
-3
No files found.
docs/heap_lang.md
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.
...
...
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