Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

Avital-Fine
Copy link
Contributor

Copy link
Collaborator

@NickCraver NickCraver left a comment

Choose a reason for hiding this comment

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

Spotted a few things cross-PR in reviewing these, notes inline! Thanks again, these PRs are fantastic and you're cranking 'em out <3

Comment on lines 1111 to 1114
/// <returns>
/// <see langword="true"/> if the element is a member of the set.
/// <see langword="false"/> if the element is not a member of the set, or if key does not exist.
/// </returns>
Copy link
Collaborator

Choose a reason for hiding this comment

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

In this case doc should say an array of these true/false, matching position, e.g.

Suggested change
/// <returns>
/// <see langword="true"/> if the element is a member of the set.
/// <see langword="false"/> if the element is not a member of the set, or if key does not exist.
/// </returns>
/// <returns>
/// An array of booleans corresponding to <paramref name="values"/>, for each:
/// <see langword="true"/> if the element is a member of the set.
/// <see langword="false"/> if the element is not a member of the set, or if key does not exist.
/// </returns>

What happens when the key isn't present, all falses?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yes

@Avital-Fine Avital-Fine requested a review from NickCraver April 11, 2022 07:23
@Avital-Fine Avital-Fine requested a review from NickCraver April 12, 2022 07:37
Copy link
Collaborator

@NickCraver NickCraver left a comment

Choose a reason for hiding this comment

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

Looking good - thank you for this!

@NickCraver
Copy link
Collaborator

Pushed one last tidy on the tests, we should nuke the key when starting to ensure a consistent test run - after that clears will merge in.

@Avital-Fine
Copy link
Contributor Author

Pushed one last tidy on the tests, we should nuke the key when starting to ensure a consistent test run - after that clears will merge in.

Right 😅

Avital-Fine added 2 commits April 12, 2022 15:20
@NickCraver NickCraver merged commit 0e9e698 into StackExchange:main Apr 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants