Skip to content

Sys, concurrent, runtime (1): filled in @param, @tparam, and @return tags that were missed last time#26119

Draft
bvenners wants to merge 1 commit into
scala:mainfrom
artimahub:scaladoc-tags-sys-concurrent-runtime-cleanup
Draft

Sys, concurrent, runtime (1): filled in @param, @tparam, and @return tags that were missed last time#26119
bvenners wants to merge 1 commit into
scala:mainfrom
artimahub:scaladoc-tags-sys-concurrent-runtime-cleanup

Conversation

@bvenners
Copy link
Copy Markdown
Contributor

As a next step in improving the Scaladoc documentation for the Scala 3 standard library, this PR fills in @param, @tparam, and @return tags for scala.sys, scala.concurrent, and scala.runtime that were missed in the previous batch of PRs. I'm submitting it as a draft PR so to get CI to run on it, to see if it breaks anything, and to start getting feedback. We automated the generation of these changes and are starting to review them. We will review them all before making the PR non-draft. Please let me know if you see anything specific that you think could be improved.

…concurrent, scala.runtime (cleanup follow-up)
@bvenners bvenners requested a review from a team as a code owner May 20, 2026 19:56
@bvenners bvenners marked this pull request as draft May 20, 2026 19:56
Copy link
Copy Markdown
Contributor

@cheeseng cheeseng left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some suggestions to improve.

*
* @param p the predicate to apply to the successful result of this `Future`
* @param executor the `ExecutionContext` on which the predicate will be executed
* @return a `Future` which will hold the successful result of this `Future` if it matches the predicate or a `NoSuchElementException`
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For the second part of the sentence, may be something like this is clearer:

... or a Future in failed state with NoSuchElementException

* @param op the fold operation to be applied to the zero and futures
* @return the `Future` holding the result of the fold
*
* @param executor the `ExecutionContext` on which the fold operation will be executed
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think will be good to be before the @return .

* @param op the reduce operation which is applied to the results of the futures
* @return the `Future` holding the result of the reduce
*
* @param executor the `ExecutionContext` on which the reduce operation will be executed
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It will be better if it is before the @return ?

* @param fn the function to be mapped over the collection to produce a collection of Futures
* @return the `Future` of the collection of results
*
* @param bf the `BuildFrom` used to construct the resulting collection `M[B]` from the values of type `B`
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Better to be before @return ?

* It never returns negative results.
*
* @param timeout the maximum time to wait, in milliseconds
* @return the elapsed wait time in milliseconds, or `0` if `timeout <= 0` or the elapsed time was negative
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This part:

or the elapsed time was negative

is a bit confusing, the original comment of 'never returns negative results' should be better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants