Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Operator annotation can reject explicit operand types in error #330

@jcflack

Description

@jcflack

A copy-pasto in a condition and gap in test coverage let this one through, with an @operator with synthetic= must not specify operand types when the operator is not synthetic. As it is most convenient to put the @Operator annotation right on a method and let the operand type(s) be inferred, this would be rarely seen in practice, nor hard to work around. But it shouldn't have gotten through.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions