Fix 2.13.13 regression in Scaladoc compilation when using Scala 3 definitions#10700
Merged
Conversation
Member
Author
|
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 |
Member
|
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? |
Member
|
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. |
Member
Author
|
@SethTisue I have added the regression test |
Member
|
51b4cc6 to
08e81d1
Compare
Member
Author
|
should be fixed now |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
.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