-
Notifications
You must be signed in to change notification settings - Fork 21
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
Case class with unusual field name kills the compiler #10625
Comments
But... why? |
Why did I use such a name? Well I just wanted to try out whether Jackson's data binding for CSV works as I expect, and adheres to the alphabetic ordering of the mangled names, and I came up with such a name by accident. The original example had multiple fields of course. |
The spec disallows embedded |
if we had a better selective-warning-suppression story, maybe there could be a warning when you use I have an urge to simply close the bug with a "well don't do that", but it's really not ideal for the compiler to crash on this, there is certainly room for improvement here. |
Closing in favor of #8831 which may not be exact duplicate but serves as umbrella for dollar-inducements. |
We are about to merge a PR (scala/scala#9008) that fixes #8831 without fixing this. Regardless, I'm leaving this one closed since as @som-snytt indicates, this is actually within spec. Regardless, a PR that added a warning would be welcome, especially now that we have convenient warning suppression. |
The text was updated successfully, but these errors were encountered: