fix: allow to generate the documentation of the stdlib #24574
Merged
Conversation
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
Member
Author
|
Note that this is not the cleanest scaladoc, it would require some polishing. |
hamzaremmal
added
the
backport:nominated
Gedochao
approved these changes
Nov 28, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Based on @bracevac remarks here #24434 (comment)
We do not need to add
-sourcepathwhen generating the scaladoc since compiling with-from-tasty(what scaladoc does) will put the TASTy in the classpath. This means that the compiler will be happy and will find the symbols.Closes #24434
Supersedes #24569, #24510.
Thanks Oliver for taking the time to analyze the issue in depth.