> Well we have overloadable Enums so that's less of an issue you just do Opt1 > and use it as such, no longer need to be worried about a prefix.
The issue is more about use with autocomplete and discover ability. Just using `Opt1` compiles but you have to either remember all the options or look them up. That’s a pain. Autocomplete is difficult to support as there’s no syntax to indicate to the LSO that you only want enum options, not aliases or variables containing enums. Personally I like Swifts `.` prefix as a generic enum marker — it’s short but unambiguous both for autocomplete and reading. It’s very clear to read `findNode(kind = .StringLit)` without needing a ‘nk’ prefix `findNode(kind = nkStringLit)`. Both are clearly enum params, whereas `findNode(kind = StringLit)` is ambiguous to a reader or autocomplete.
