Fix global capabilities support in scaladoc - #25563
Merged
Merged
Conversation
natsukagami
approved these changes
Mar 19, 2026
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
4 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.
Fixes #25529
In the case of
usesanduses_init, the tasty parser in scaladoc would run into an infinite cycle trying to resolve owners. This seems to be specific to term refs mutuallyreferring to each other in the capture sets/@retains annotation of classes.
I was unable to produce a diverging example in non-CC mode that involves only types in annotations.
Additionally, implements proper scaladoc rendering of
usesanduses_init.How much have your relied on LLM-based tools in this contribution?
Used Codex to analyze the problem.
How was the solution tested?
Manually, and with new regression tests in the scaladoc suite.