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
  • Issues
  • #146
Closed
Open
Issue created Jan 26, 2018 by Jacques-Henri Jourdan@jjourdanMaintainer

Lemmas about updates should be instantiated by default witht the current BI instead of `iProp`

The instances for the FUpd and FUpdFacts type classes are set in a way that gives the priority to iProp? Therefore, when using lemmas about updates in vProp, we sometimes have to manually instantiate them with the current BI. Otherwise, the lemmas are instantiated with iProp and used through the embedding.

See, for example https://gitlab.mpi-sws.org/FP/sra-gps/blob/gen_proofmode_WIP/theories/examples/circ_buffer.v#L236

The instances for the AsValid type class prioritizes the fact of not using the embedding, so we should be able to fix this issue by simply making sure the search for AsValid occurs before FUpd, but I do not know how to do that.

@robbertkrebbers, any idea?

Assignee
Assign to
Time tracking