Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add messages to some asserts in std/socket.d #7039

Merged
merged 1 commit into from
May 25, 2019
Merged

Add messages to some asserts in std/socket.d #7039

merged 1 commit into from
May 25, 2019

Conversation

Flying-Toast
Copy link
Contributor

Work on project #2

@dlang-bot
Copy link
Contributor

Thanks for your pull request and interest in making D better, @Flying-Toast! We are looking forward to reviewing it, and you should be hearing from a maintainer soon.
Please verify that your PR follows this checklist:

  • My PR is fully covered with tests (you can see the annotated coverage diff directly on GitHub with CodeCov's browser extension
  • My PR is as minimal as possible (smaller, focused PRs are easier to review than big ones)
  • I have provided a detailed rationale explaining my changes
  • New or modified functions have Ddoc comments (with Params: and Returns:)

Please see CONTRIBUTING.md for more information.


If you have addressed all reviews or aren't sure how to proceed, don't hesitate to ping us with a simple comment.

Bugzilla references

Your PR doesn't reference any Bugzilla issue.

If your PR contains non-trivial changes, please reference a Bugzilla issue or create a manual changelog.

Testing this PR locally

If you don't have a local development environment setup, you can use Digger to test this PR:

dub fetch digger
dub run digger -- build "master + phobos#7039"

@Flying-Toast
Copy link
Contributor Author

I'm not sure what the message should be for this assert:

assert(result.data.length > 0);

@thewilsonator
Copy link
Contributor

Failed to retrieve AddressInfo? Not surer why thats an assert rather that an ErrnoException (or something a bit more descriptive).

cc @CyberShadow git blame blames you as author of the assert in question. Any insight?

@lesderid
Copy link
Contributor

lesderid commented May 25, 2019

AFAICT that can never happen, so that assert can probably be removed. Both POSIX[1] and Windows[2] will always return "one or more" results when getaddrinfo returns 0, so that should already be handled by:

enforce(ret == 0, new SocketOSException("getaddrinfo error", ret, &formatGaiError));

[1] https://pubs.opengroup.org/onlinepubs/9699919799/functions/getaddrinfo.html
[2] https://docs.microsoft.com/en-us/windows/desktop/api/ws2tcpip/nf-ws2tcpip-getaddrinfo

@Flying-Toast
Copy link
Contributor Author

I think that

static assert(0);
could also be removed, because it is already covered by
static assert(0); // No socket support yet.
?

@dlang-bot dlang-bot merged commit a420745 into dlang:master May 25, 2019
@lesderid
Copy link
Contributor

I think it's better to keep that. If the static assert(0) is removed, what should it return?

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.

4 participants