Skip to content

Represent user inputs via traits, rather than a large enum #321

@alice-i-cecile

Description

@alice-i-cecile

The exhaustive approach is lovely, but a) leads to some very tricky nesting b) isn't user extensible c) results in excessive memory use, as every input requires the maximum amount of space.

In addition:

          I think this will be obsolete if we use traits instead of enums to represent the user input, which is probably the better move in the long run.

Originally posted by @TimJentzsch in #241 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    code-qualityMake the code faster or prettiercontroversialRequires a heightened standard of review

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions