Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Iris Iris
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 171
    • Issues 171
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 14
    • Merge requests 14
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Iris
  • IrisIris
  • Merge requests
  • !707

Formulate `is_closed_expr` in terms of `gset`s.

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Dan Frumin requested to merge dfrumin/iris-coq:is_closed_gset into master Jun 20, 2021
  • Overview 39
  • Commits 3
  • Pipelines 15
  • Changes 2

..And prove some additional lemmas.

Following a discussion w/ @robbertkrebbers

Since it is not necessary for is_closed_expr to simplify well, it might be better to formulate it in terms of sets, not lists. This is convenient when you have e.g. a description of a type system where contexts are maps, and you want to prove that all well-typed expressions are appropriately closed.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: is_closed_gset