-
Notifications
You must be signed in to change notification settings - Fork 113
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
Ideally, there would be a distinct attribute for these "invented" handle types #1533
Comments
There are many manufactured NativeTypeDefs. How would you want those treated? |
Yes, I'm not sure how you'd untangle it as the metadata is increasingly tailored for the non-systems language consumers and you wouldn't want to break that. I may just fix this on my end. |
Below are all the manufactured How do we want to handle these assuming we want to reserve These all should still support
|
Ideally, there would be a distinct attribute for these "invented" handle types, like
MEMORYMAPPEDVIEW_HANDLE
, to distinguish them from native types defs that are actually defined in the Windows SDK. Without this, languages like C++ and Rust that aim to preserve the original definitions more faithfully are now stuck not being able to distinguish between something likePSID
which is actually defined by the Windows SDK andMEMORYMAPPEDVIEW_HANDLE
which is not. I thought this was what theNativeTypeDef
attribute was for but perhaps I misunderstood.Originally posted by @kennykerr in #561 (comment)
The text was updated successfully, but these errors were encountered: