Update instructions for parallel-letter-frequency (#2713) #2752
Conversation
This file contains 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
The exercise docs suggested that the submitted code is automatically tested for the usage of parallelism. This is not the case, so the paragraph rewritten to instead suggest students to check for parallelism themselves. To help, a few links to resources about concurrency and parallelism in Java are added.
manumafe98
reviewed
Mar 18, 2024
exercises/practice/parallel-letter-frequency/.docs/instructions.append.md
Outdated
Show resolved
Hide resolved
The fact that the tests are currently not checking for parallelism is no longer mentioned in the instructions. Resources about concurrency are moved to `hints.md`.
Co-authored-by: Sander Ploegsma <[email protected]>
sanderploegsma
approved these changes
Mar 21, 2024
|
Thanks for your contribution @yogan! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
See #2713
The exercise docs suggested that the submitted code is automatically
tested for the usage of parallelism. This is not the case, so the
paragraph rewritten to instead suggest students to check for parallelism
themselves.
To help, a few links to resources about concurrency and parallelism in
Java are added.
Reviewer Resources:
Track Policies