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 122
    • Issues 122
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 15
    • Merge Requests 15
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Iris
  • Iris
  • Issues
  • #51

Closed
Open
Created Dec 16, 2016 by Ralf Jung@jungOwner

iApply: Add sufficiently many [] spec patterns per default?

I find my self repeatedly writing iApply (foo with "[] [] []") in lambdaRust proofs. Would it make sense to extend the automatic "adding a [] to the end of th spec pattern list" that iApply does, such that it will add as many [] as are needed to get the job done? Essentially, iApply foo would always succeed if the conclusion of foo matches the goal, and all assumptions will only get the persistent contect -- spec patterns are only needed if one wants to give more than that? IMHO that would also improve the general workflow of working with iApply since I don't need to look up in advance how many items I need to put into the spec pattern, I can just iApply and then see which of the goals I get need further resources.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None