Skip to content

do not check for programming failures in --fail-on-assertion-only #735

@zapashcanon

Description

@zapashcanon

In the code, where we check for an OOB or a division by zero, the boolean corresponding to the failure is passed to select. Instead we should simply assume it does not fail and avoid calling the solver twice.

The converse holds for assertions in --fail-on-trap-only

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions