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

windows-sys: use ADDRESS_FAMILY for sa_family_t #463

Merged
merged 1 commit into from
Aug 27, 2023
Merged

windows-sys: use ADDRESS_FAMILY for sa_family_t #463

merged 1 commit into from
Aug 27, 2023

Conversation

nerditation
Copy link
Contributor

originally Windows SDK didn't have a sa_family_t typedef, and we requested win32metadata to add it (microsoft/win32metadata#1538) and used that from windows-sys as our sa_family_t definition on Windows platform (#414), which was an oversight. after all, Winsock2 isn't compliant to Posix and has it's own naming scheme, and ADDRESS_FAMILY is intended to be the equivalence of sa_family_t.

fixes #462

originally Windows SDK didn't have a `sa_family_t` typedef, and we
requested `win32metadata` to add it (microsoft/win32metadata#1538)
and used that from `windows-sys` as our `sa_family_t` definition on
Windows platform (#414), which was an oversight. after all, Winsock2
isn't compliant to Posix and has it's own naming scheme, and
`ADDRESS_FAMILY` is intended to be the equivalence of `sa_family_t`.
@Thomasdezeeuw Thomasdezeeuw merged commit 60e59ee into rust-lang:master Aug 27, 2023
36 of 37 checks passed
@Thomasdezeeuw
Copy link
Collaborator

Thanks @nerditation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Windows: sa_family_t should use ADDRESS_FAMILY from windows-sys
2 participants