-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect names for enum values #1958
Comments
@OlegYch Interesting, thank you for reporting! This scales, unfortunately, Reaching out to the JVM for a universal solution here seems the way to completely solve this problem, at the expense of the names it would generate:
At the very least they'd be unique, and we'd only need to interpolate them in the case of disambiguation, so maybe it's alright that the names are not good. What do you think? |
i think the usual quoting is enough, eg:
|
Possibly in Scala, but Java will have this problem. I guess we could do both, each language having their own experience. |
Oh, perhaps it's possible to borrow name mangling scheme from scala.
…On Thu, Mar 7, 2024, 23:22 Devon Stewart ***@***.***> wrote:
Possibly in Scala, but Java will have this problem. I guess we could do
both, each language having their own experience.
—
Reply to this email directly, view it on GitHub
<#1958 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACBQGBUPSPG26QP3OQV4V3YXDSDPAVCNFSM6AAAAABELERPTGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBUGYZDONJVGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
For a enum like this
guardrail will generate two objects with same name
Datetime
The text was updated successfully, but these errors were encountered: