Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
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 23
    • Merge Requests 23
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Iris
  • Iris
  • Issues
  • #138

Closed
Open
Opened Jan 18, 2018 by Ralf Jung@jungOwner0 of 4 tasks completed0/4 tasks

wp_apply/Texan triple improvements

  • wp_apply could be able to apply a total WP when the goal is a partial WP, removing some duplication in heap_lang/lib.
  • wp_apply could automatically try to prove that the expression is not a value, and then apply some variant of wp_step. This would remove the need to have a \later in the definition of Texan triples, making them equivalent to a WP in all cases (as opposed to just the non-value case). I think right now I regret that we decided for Texan triples to contain the \later, this makes them slightly harder to teach and destroys their equivalence with WP/"normal" triples.
  • [More far-fetched?] Make the precondition of Texan triples a list of assertions, so that we can (a) desugar them to something curried, and (b) not have silly True preconditions when the list is empty.
  • When proving a triple, the postcondition could be wrapped in a fancy update, removing the need to rewrite -wp_fupd in some of our proofs. Of course, when applying a triple, that update must not be in the way.

Blocked by #130

Edited Nov 26, 2020 by Ralf Jung
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: iris/iris#138