Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
L
lambda-rust
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
Model registry
Operate
Environments
Monitor
Service Desk
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
Iris
lambda-rust
Commits
2c6fbd2f
Commit
2c6fbd2f
authored
5 years ago
by
Hai Dang
Browse files
Options
Downloads
Patches
Plain Diff
update README
parent
1ed0960a
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Pipeline
#20193
canceled
5 years ago
Stage: build
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+24
-0
24 additions, 0 deletions
README.md
with
24 additions
and
0 deletions
README.md
+
24
−
0
View file @
2c6fbd2f
...
@@ -163,6 +163,30 @@ lifetime logic is in [lifetime_sig.v](theories/lifetime/lifetime_sig.v).
...
@@ -163,6 +163,30 @@ lifetime logic is in [lifetime_sig.v](theories/lifetime/lifetime_sig.v).
| LftL-fract-shorten | frac_borrow.v | frac_bor_shorten |
| LftL-fract-shorten | frac_borrow.v | frac_bor_shorten |
| LftL-fract-iff | frac_borrow.v | frac_bor_iff |
| LftL-fract-iff | frac_borrow.v | frac_bor_iff |
### Verification of Full Arc
We do not have the
**Core Arc**
example (Section 3.3 of the RBrlx paper) in Coq.
Instead, we have the
**Full Arc**
example (Section 5.3 of the RBrlx paper, also
Section 6 of its technical appendix).
The verification of Full Arc is split into 2 parts:
1.
Verifying Full Arc with respect to some abstract specification. This is done
in
[
lang/arc.v
](
theories/lang/arc.v
)
, with the help of a CMRA (PCM) defined in
[
lang/arc_cmra.v
](
theories/lang/arc_cmra.v
)
.
The specification is proven in the
`*_spec`
lemmas.
More comments can be found in the aforementioned files.
2.
Verifying that the abstract specification implies the semantics
interpretation of the type of Arc and Weak. This can be found in
[
typing/lib/arc.v
](
theories/typing/lib/arc.v
)
.
In this file,
*
the
`Program Definition arc (ty : type)`
and
`Program Definition
weak (ty : type)`
are the interpretations of the
`Arc<ty>`
and
`Weak<ty>`
types, respectively.
*
`arc_send`
,
`arc_sync`
,
`weak_send`
,
`weak_sync`
prove that both
`Arc<ty>`
and
`Weak<ty>`
correctly implement the
`Send`
and
`Sync`
traits.
*
The
`*_type`
lemmas prove that each function semantically satisfies its
syntactic type.
## For Developers: How to update the GPFSL dependency
## For Developers: How to update the GPFSL dependency
*
Do the change in [GPFSL], push it.
*
Do the change in [GPFSL], push it.
...
...
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