Skip to content

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

Closed
Open
Opened Apr 01, 2019 by LAWALL Julia@lawall
  • Report abuse
  • New issue
Report abuse New issue

improve VC localization for invariants

Another case where why3 isn't really in the place that one wants, is when one has an invariant in a function that is larger than what one can see on the screen. It seems that for invariants, why3 always considers the name of the function to be relevant (orange), whereas I would rather see the invariant that I am working on.

Edited Apr 01, 2019 by MARCHE Claude
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: why3/why3#296