Skip to content

Remove wildcard pattern in exhaustive enums #1924

@lgingerich

Description

@lgingerich

Is your feature request related to a problem or challenge?

Multiple instances of match expressions over the PrimitiveType use a wildcard even though the enum is exhaustive. If more types were to be added to PrimitiveType, this wildcard would silently swallow usage of those types. Some of these instances currently throw ErrorKind::FeatureUnsupported. They also have hardcoded Timestamptz since it's the only unsupported type. Examples can be seen here and here.

This issue is to document and fix instances of wildcard usage in exhaustive enums.

Describe the solution you'd like

  • Remove wildcard in exhaustive match expressions
  • Add necessary attributes for exhaustive enums in match expressions

Willingness to contribute

I can contribute to this feature independently

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions