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
0
Issues
0
List
Boards
Labels
Service Desk
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Operations
Operations
Incidents
Environments
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Rodolphe Lepigre
Iris
Commits
598a6902
Commit
598a6902
authored
Oct 05, 2018
by
Ralf Jung
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
wp_fork changelog
parent
d7934087
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
2 deletions
+3
-2
CHANGELOG.md
CHANGELOG.md
+3
-2
No files found.
CHANGELOG.md
View file @
598a6902
...
...
@@ -24,8 +24,8 @@ Changes in and extensions of the theory:
functions.
*
[#] Add atomic updates and logically atomic triples, including tactic support.
See
`heap_lang/lib/increment.v`
for an example.
*
[#] HeapLang now uses right-to-left evaluation order. This makes
easier to
write specifications of curried functions.
*
[#] HeapLang now uses right-to-left evaluation order. This makes
it
significantly easier to
write specifications of curried functions.
Changes in Coq:
...
...
@@ -78,6 +78,7 @@ Changes in Coq:
*
`namespaces`
has been moved to std++.
*
Changed
`IntoVal`
to be directly usable for rewriting
`e`
into
`of_val v`
, and
changed
`AsVal`
to be usable for rewriting via the
`[v <-]`
destruct pattern.
*
`wp_fork`
is now written in curried form.
## Iris 3.1.0 (released 2017-12-19)
...
...
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