Skip to content

Action items for compatibility-breaking release #1148

Closed
@tautschnig

Description

@tautschnig

We should consider dropping some cruft; doing so will break compatibility and thus must happen in one major release (and only one). Requires an increment of the goto binary format version.

  • Drop symbol_typet and ns.follow (and use tag types instead)
  • Restrict gotos to a single target
  • Add a width to pointers (and remove all config references from solvers)
  • Clean up the interface between cbmc and others (e.g., hw-cbmc, 2ls, ebmc, cegis)
  • Replace owning raw pointers #835

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions