-
Notifications
You must be signed in to change notification settings - Fork 21
scalac unable to parse java annotations in a file in the empty package with no imports #4071
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
Labels
Milestone
Comments
Imported From: https://issues.scala-lang.org/browse/SI-4071?orig=1 |
@retronym said: @X
public @interface Annot {
}
@interface X {} |
anne-decusatis
added a commit
to anne-decusatis/ratatool
that referenced
this issue
Aug 21, 2019
Sometimes these are generated without a namespace Then, we fail to compile because of this Scala bug: scala/bug#4071 We can make sure it gets generated with a namespace by specifying namespace this is valid avro per https://avro.apache.org/docs/current/spec.html#Enums
anne-decusatis
added a commit
to spotify/ratatool
that referenced
this issue
Aug 21, 2019
Sometimes these are generated without a namespace Then, we fail to compile because of this Scala bug: scala/bug#4071 We can make sure it gets generated with a namespace by specifying namespace this is valid avro per https://avro.apache.org/docs/current/spec.html#Enums
anne-decusatis
added a commit
to spotify/ratatool
that referenced
this issue
Aug 23, 2019
* First pass at CircleCI config.yml based on bits of Scio's config.yml * Remove the invalid(?) yaml & and * * Define jobs outside of build workflow * Fix line breaks in sbt command definition * Remove Travis build * Add namespace to TestRecord enum & fixed (#166) Sometimes these are generated without a namespace Then, we fail to compile because of this Scala bug: scala/bug#4071 We can make sure it gets generated with a namespace by specifying namespace this is valid avro per https://avro.apache.org/docs/current/spec.html#Enums
Scala 3 still has the issue, though (as of 3.7.0-RC1). if that's a concern to anyone, please open a ticket in the Scala 3 tracker |
This was Dotty |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
One wonders what our test suite is doing exactly given that this java file is verbatim from a currently active test.
Here is the file.
It is successfully parsed if written like this:
The text was updated successfully, but these errors were encountered: