Conversation
Documents declarations that had no doc comment at all in the root of scala.collection: the Iterable, Seq, Set and Map hierarchies and their Ops traits, the views, the steppers and the factory machinery. Comment-only: no declaration, body, import, annotation or blank line is touched.
bvenners
force-pushed
the
scaladoc-missing-docs-collection-core
branch
from
September 10, 2026 06:38
67a3db7 to
23fb295
Compare
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
1 participant
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.
This PR fills in a main doc comment plus @PARAM, @tparam, and @return tags for the root of
scala.collectionthat is completely missing any Scaladoc documentation. It covers theIterable,Seq,SetandMaphierarchies and theirOpstraits, the views, the steppers and stepper shapes, and the factory and build-from machinery. I'm submitting it as a draft PR so that I can get the CI to run on it, to see if it breaks anything, and to start getting feedback. We automated the generation of these changes and have not reviewed all of them yet. We will review them all before making the PR non-draft. Please let me know whether you think this is going in the right direction in general, and anything specific that you notice that could be improved.