Olivier Halligon

Final sleepy late thought: don't we want the destination, appropriately typed, as an associated value of each case? Or maybe I'm confusing with another PR 😓 But anyway if we...

I think on call site you could also just use it as Swift intends, that is, this should work? (didn't try it though) ``` print(Translation.Food.`Type`.apple) ``` As @djbe said, that's...

What's strange is that I'd expect that we'd have a similar issue with `self`, but it doesn't seem to bother the compiler like with `.Type`… ```swift public enum Translation {...

yeah, I was actually editing my comment above to add: > So not sure why adding backticks around `Type` inside the `print` wouldn't similarly solve the issue… might actually be...

For reference: https://bugs.swift.org/browse/SR-9897

This was started in #108 but the author or this PR never gave news to my comments and requests for changes 😢 Especially I think this feature could be generalised...

@djbe but then that could just be a special template that just works well with `Reusable` 😉 @RomanVolkov Yeah, that was my idea. Maybe I'm overthinking this generalisation of the...

Thanks for the PR (and sorry for the late reply) Could you update the contexts files with this new code so we can see how the updated YAML contexts look...

Yeah what you probably want is to convert your `Unicode.Scalar` into a `Character`, not a `UniChar` https://developer.apple.com/documentation/swift/character/2906502-init in Unicode, code points are not limited to 2^16 so it's not logical...

Also, you mention in the PR description that you have a template that includes those glyph names but kept it as a gist and didn't include it in the PR,...