leanprover-community / leanprover-community/iris-lean

iframe alterations

Open
#438 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

proof-mode
Dominant language
Lean
Stars
218
Forks
63
Avg merge
1d 23h
Merged PRs (30d)
22

Description

Right now, iframe is a faithful port of Rocq's tactic. However, there are some changes we may consider making to tweak its behavior. This issue is here to consider and discuss potential tweaks to the tactic.

  1. iframe does not eliminate emp (eg. in the goal P ∗ emp)
  2. iframe automatically uses Iris hypotheses, but not pure hypotheses. It will not frame out P ∗ ⌜φ⌝ even if φ is a pure hypothesis you have exactly.
  3. Adding a hypothesis to iframe actually causes it to use less facts, as it will try to solve the framing goals using only the supplied arguments

Idea for 2/3: Change the iframe syntax to be more like simp and grind

  • iframe can be whatever behavior we decide we want to be the default
  • iframe H (including pure syntax like iframe %P) to include additional hypotheses in the set iframe uses
  • iframe only H for the existing behavior of iframe H

I wonder even if we can implement iframe? to help squeeze internal iframe statements. Probably not a big deal since iframe operates on a much smaller scale than simp anyways.

The genesis for this suggestion was that I was using iframe, I need to add a pure hypothesis, and I found it sort of annoying to have to go through and figure out all the names of stuff iframe was picking up on, just write them all out plus supply it this one additional pure hypothesis.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue identifies the iframe tactic as the entry point but names no files or tests. First inspect its implementation and current behavior, then settle the intended default, hypothesis-selection syntax, and whether iframe? is in scope; done requires a recorded decision and corresponding tests.

Written by the indexing model from the issue text.

Assessment

Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.