-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Fix documentation generation from tasty with sourcepath #24569
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
b57b358 to
77f0489
Compare
We don't run cc when we compile |
77f0489 to
8c14f5a
Compare
|
|
||
| /** Is captureChecking enabled for any of the currently compiled compilation units? */ | ||
| /** Is captureChecking enabled for any of the currently compiled compilation units? | ||
| * Disabled when compiling from tasty since capture checking was already performed. |
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.
There are some non-standard ways of stopping the compiler after emitting TASTy and before performing capture checking. This is then factually false.
|
It's something else that causes the issue. |
Filter out -sourcepath from doc scalacOptions as it causes conflicts with symbols loaded from tasty during documentation generation.
8c14f5a to
28389d2
Compare
|
Hamza beat me to it |
Based on @bracevac remarks here #24434 (comment) We do not need to add `-sourcepath` when 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.
Filter out -sourcepath from doc scalacOptions as it causes conflicts
with symbols loaded from tasty during documentation generation.
Fixes #24434