Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in
why3
why3
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 59
    • Issues 59
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 7
    • Merge Requests 7
  • Registry
    • Registry
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Commits
  • Issue Boards
  • Why3
  • why3why3
  • Issues
  • #151

Closed
Open
Opened Jun 27, 2018 by Andrei Paskevich@paskevyc
  • Report abuse
  • New issue
Report abuse New issue

split_vc breaks splitting of "[@case_split]" conditions

split_goal_right + split_goal_right works correctly: first it splits the goal on the right, then the [@case_split] premises.

split_vc + split_vc does not work because of introduce_premises. This makes split_vc pretty much incompatible with SP (aka fast WP) which relies heavily on [@case_split].

Possible solutions:

  • make split_goal_right work on local premises (generated by introduce_premises)
  • make split_vc use a special variant of split_goal_right that works on local premises
  • make split_vc reassemble the local premises before splitting them with split_goal_right
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
No due date
0
Labels
None
Assign labels
  • View project labels
Reference: why3/why3#151