Skip to content

Verification plan for invariant generation #21

@jeroenk

Description

@jeroenk

At a high level can one define a verification plan, where the available options are linked together abstractly. Try to apply the same idea for invariant generation. This seems to be of general importance in verification tools; can we build some generic infrastructure to support it?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions