Skip to content

suggestion: reword "x should equal y" to "expected y\ninstead got x" or similar #28

@namedots

Description

@namedots

the current wording, while correct, seems to clash a bit with beginner expectations, it can easily be misread as "given input x, expected y"

the (especially beginner) solver is likely not even aware of what the assertion looks like, and therefore doesn't have the context for the message

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