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
@specialize vs. @inline: @specialize still wins #8247
Comments
Imported From: https://issues.scala-lang.org/browse/SI-8247?orig=1 |
can someone verify if this is still an issue in Scala 2.12.x? |
@SethTisue In Scala 2.12, it requires option switch
|
@texasbruce Thanks for the verification. I edited the description of this issue to steps, problem, expectation format. |
steps
problem
m2
is not inlined.expectation
The bytecode of methods
m1
andm2
both are constant true.original report
I'm not sure I understand what happened in #5005. It's clearly a bug, I opened it with a clear description of the bug, but it ended up being closed because it had become "confused". Okay, I will unconfuse things. Here is the same report again. One should not have to choose between
@specialized
working and@inline
working.The text was updated successfully, but these errors were encountered: