Skip to content

[safety] Inconsistent use of "*X* safe operation" #48

@lucteo

Description

@lucteo

The document defines X safe operation through:

An X safe operation upholds some safety property X even if preconditions are violated.

Later on the document drops the X qualification:

A safe operation will never exhibit undefined behavior, even if preconditions are violated.

The document should use the X qualification in all places, or add a footnote explaining why it doesn't add value anymore.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    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