-
Notifications
You must be signed in to change notification settings - Fork 90
Async.async gives "nullary-override" warning when not provided with explicit type #238
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
Comments
@retronym it came up in the Scala community build that this problem will become more acute with the release of Scala 2.13.3, because @dwijnand's scala/scala#8846 makes this warn by default
|
@shubhamJay as a workaround, I'd suggest using |
This problem will go away in scala-async 1.0, which I plan to release in July (once Scala 2.12.12 and 2.12.3 are out.)
It may also be possible to get rid of the warning in scala-async 0.10.x by tracking down what part of the macro expansion runs afoul of the warning and inserting the parens. |
The tree in question is:
This should be It is generated in
To fix, the |
Any info on that scala-async 1.x release? I am noticing these warnings with scala 2.13.6. To get rid of the warnings I needed to explicitly set the types return types when using Thanks! |
While compiling the above code with compiler option "-Xlint:nullary-override" enabled on scala 2.13.2 version, the first line throws an warning saying
nullary method assumes an empty parameter list from the overridden definition
. After providing explicit type, the warning goes away as written on second line.The text was updated successfully, but these errors were encountered: