Skip to content

Confusing error message when there's no subenum yet #42

@KSXGitHub

Description

@KSXGitHub

When I add #[subenum(Sub)] to the top of the enum before declaring its variant, an error message would appear:

expected pattern, found `,`

This error is confusing. I suggest improving this error message to points out the cause directly, or make it disappear.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions