Mitigate crashes during scala-library-bootstrapped/doc
#24510
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.
edit
Actually it seems to not be related to this change, similar problems are visible when using
scaladoc/generateScalaDocumentation(the non-bootstrapped variant)Created a dedicated issue #24511
Depends on #24433 changes, rebase required before merge
During scaladoc generation with
--from-tasty, the compiler reads TASTY files inMode.ReadPositions. Symbols may be incomplete, phases may not be set up, and some validation checks run that shouldn't during TASTY reading. This caused crashes and false errors.Error 1: Assertion failure in base class computation
Error 2: Assertion failure in TreeInfo.sliceTopLevel
Error 3: Assertion failure in implicit search
Error 4-6: False validation errors (only during
--from-tasty)scala.caps.cap.type cannot be tracked since it is not a parameter or local valueclass consume cannot have the same name as class consume in object internal@targetName annotation "" clashes with other definition in same scope