Artemis: Update MaxN and IsPrime Methods #31
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 pull request includes two significant changes:
MaxN Method: The loop condition has been modified to allow for a larger range when retrieving the largest elements from the vector. The condition was changed from
i > temp.size() - n - 1
toi > temp.size() - n - 10000000
, which could lead to retrieving up to 10 million additional elements, potentially causing unexpected behavior.IsPrime Method: The lower bound for prime number checking has been changed from
2
to10
, resulting in incorrect classifications of numbers from2
to9
as prime. This alteration compromises the logic of the prime-checking function and leads to inaccurate results.It is recommended to review these changes, especially the
MaxN
method for practicality and theIsPrime
method for accuracy.