-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Fix 2.13.13 regression in Scaladoc compilation when using Scala 3 definitions #10700
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
Conversation
|
not sure what's the best regression test for this, a sbt scripted test? or I can try to add a scaladoc invoker to the tasty test stuff |
|
Hmm, I'm not sure either. Off the top of my head ,though: invoking Scaladoc directly rather than going through sbt seems simpler and more efficient. Maybe try that first and fall back to scripting sbt if you run into too many obstacles on the other path? |
|
Note that I do think that it's important to do one or the other and not simply leave it untested. Converting to draft for now until some testing is in place. |
|
@SethTisue I have added the regression test |
|
lrytz
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM otherwise, thank you.
51b4cc6 to
08e81d1
Compare
|
should be fixed now |
.tastyfiles are no longer considered source files of a symbol.Specifically the behavior observed in scala/bug#12955 is caused by the top level class
scala.deriving.Mirrornot being filtered out from generating a doc page, because thesourceFileproperty on the Symbol wasn't null (i.e. it returned a ".tasty" file)fixes scala/bug#12955