-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Be more specific about winapi features #4737
Comments
I disabled all of the winapi features that are on by default and, at least on my build, it doesn't seem to raise any issues. Might be on my end, let me run the CI just to be sure. |
The features were added like this to fix #4662, so if you remove them, that issue should come back. (Of course, only on windows builds.) |
try to work on this, I am new to rust, and can you help below question @Darksonn in in below codes, as I understand
|
The It exists because Tokio replaces it with something else when building documentation to show windows stuff in docs built on Linux. |
@Darksonn , tests pass with above change in PR, I am unclear why we do not have error regarding unresolved import even though in
|
This issue can be closed because the PR merged? @Darksonn |
Ah, thanks. I didn't notice that the PR wasn't set up to auto-close this issue when merged. |
Our dependency on winapi is listed in the following way:
Additionally, the various features of Tokio that require something from winapi can enable additional winapi features, e.g.:
However, the features that are listed in the
[target.'cfg(windows)'.dependencies.winapi]
section are also specific to various other features of Tokio, and hence enabled more often than necessary. We would like to be more specific about which features we need, and only enable each feature when we need it by moving them to be listed on other dependencies like "winapi/namedpipeapi".The text was updated successfully, but these errors were encountered: