Skip to content

Surprising/incorrect behavior for X is not equal to Y or Z #28

@Page-

Description

@Page-

X is not equal to Y or Z is parsed as X is not equal to Y or X is not equal to Z which doesn't make sense as it'd always be true and thefore unnecessary and would violate the maxim of quantity. It would instead make sense to be interpreted as X is not (equal to Y or equal to Z)

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