Skip to content

Conversation

@logiclrd
Copy link
Contributor

@logiclrd logiclrd commented Jun 2, 2024

The Socket.Select documentation states that ArgumentNullException is thrown if any of checkRead, checkWrite or checkError is empty/null. But, null or empty collections can be passed for them. The real requirement is that at least one of them must contain at least one socket. It is perfectly okay to select(read_sockets, NULL, NULL) or select(NULL, write_sockets, NULL) or select(NULL, NULL, error_sockets).

The Socket.Select documentation states that `ArgumentNullException` is
thrown if any of checkRead, checkWrite or checkError is empty/null. But,
null or empty collections can be passed for them. The real requirement
is that at least one of them must contain at least one socket. It is
perfectly okay to `select(read_sockets, NULL, NULL)` or `select(NULL,
write_sockets, NULL)` or `select(NULL, NULL, error_sockets)`.
@dotnet-policy-service dotnet-policy-service bot added the community-contribution Indicates that the PR has been added by a community member label Jun 2, 2024
@dotnet-policy-service
Copy link
Contributor

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

@ManickaP
Copy link
Member

ManickaP commented Jun 3, 2024

If you want this to get into official docs, you also need to update it in https://github.com/dotnet/dotnet-api-docs. The triple slash comments are used only for initial docs import for new APIs.

cc @antonfirsov

@wfurt
Copy link
Member

wfurt commented Jun 3, 2024

It may be worth of doing the api-docs first to nail down working with docs people.

@antonfirsov
Copy link
Contributor

@logiclrd can you please open a PR against https://github.com/dotnet/dotnet-api-docs?

You would need to edit https://github.com/dotnet/dotnet-api-docs/blob/main/xml/System.Net.Sockets/Socket.xml. If you feel it's too much of burden feel free to open an issue instead of a PR describing your recommendation.

Closing, since this repo is not he source of truth for the docs.

@antonfirsov antonfirsov closed this Jun 3, 2024
@logiclrd
Copy link
Contributor Author

logiclrd commented Jun 3, 2024

Okay :-) Thanks.

@logiclrd
Copy link
Contributor Author

logiclrd commented Jun 3, 2024

If a PR gets accepted there, will it update the docs here, or do they need to be updated here too even though it's not the source of truth?

@logiclrd
Copy link
Contributor Author

logiclrd commented Jun 4, 2024

dotnet/dotnet-api-docs#9992

@antonfirsov
Copy link
Contributor

If a PR gets accepted there, will it update the docs here, or do they need to be updated here too even though it's not the source of truth?

I must admit that I'm confused about the synchronization process myself, but I believe we don't do it with small manual PR-s. @carlossanlop can you give some hints?

@karelz karelz added this to the 9.0.0 milestone Jun 24, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Jul 25, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

area-System.Net.Sockets community-contribution Indicates that the PR has been added by a community member

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants