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
Gaëtan Gilbert
Iris
Commits
b48f20f4
Commit
b48f20f4
authored
1 year ago
by
Ralf Jung
Browse files
Options
Downloads
Patches
Plain Diff
changelog
parent
df70dbe8
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
CHANGELOG.md
+11
-0
11 additions, 0 deletions
CHANGELOG.md
with
11 additions
and
0 deletions
CHANGELOG.md
+
11
−
0
View file @
b48f20f4
...
...
@@ -118,6 +118,8 @@ Coq 8.13, 8.14, and 8.15 are no longer supported.
*
Fix
`greatest_fixpoint_ne'`
accidentally being about the least fixpoint.
*
Add
`Plain`
instance for
`|==> P`
when
`P`
is plain.
*
Rename
`bupd_plain`
→
`bupd_elim`
.
*
Change notation for atomic updates and atomic accessors to use
`<{ ... }>`
instead of
`<< ... >>`
. This avoids a conflict with Autosubst.
**Changes in `proofmode`:**
...
...
@@ -182,6 +184,15 @@ Coq 8.13, 8.14, and 8.15 are no longer supported.
*
Remove
`frac_validI`
. Instead, move to the pure context (with
`%`
in the proof
mode or
`uPred.discrete_valid`
in manual proofs) and use
`frac_valid`
.
**Changes in `program_logic`:**
*
Change the notation for logically atomic triples: we add support for specifying private (non-atomic) postconditions,
and we avoid a notation conflict with Autosubst. The new notation looks as follows:
`<<{ ∀∀ x, atomic_pre x }>> code @ ∅ <<{ ∃∃ y, atomic_post x y | z, RET v, non_atomic_post x y z }>>`
.
To keep the notation without private postcondition consistent, the way the return value is specified changes slightly
even when there is no private postcondition:
`<<{ ∀∀ x, atomic_pre x }>> code @ ∅ <<{ ∃∃ y, atomic_post x y | RET v }>>`
.
**Changes in `heap_lang`:**
*
Move operations and lemmas about locations into a module
`Loc`
.
...
...
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