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
Metadata needs to report calling convention correctly #1133
Comments
Examples include functions like |
I checked the latest CI build and it doesn't seem to capture anything to do with calling convention - still reports stdcall/winapi. Was hoping the ClangSharp update would have automagically fixed this. 😜 |
I just figured out I was feeding ClangSharp something that was forcing everything to be winapi. Now I'm properly seeing cdecl so I can add it to the metadata. One side effect is now methods/delegates previously reported as winapi are stdcall. If I see a stdcall should I report them as winapi, or use stdcall? |
I'm going to leave stdcall functions as winapi to reduce the noise. |
Related: #1053 |
I believe |
Right. It's weird the enum has both winapi and stdcall. |
Those are likely because those functions aren't
stdcall
at all - many are likelycdecl
. It would be most helpful if those are reported to the win32metadata repo since the metadata would need to indicate the calling convention before the Rust project can do anything about it.As of now, we just assume all functions are
stdcall
since the metadata doesn't appear to set the CallingConvention field.Originally posted by @kennykerr in microsoft/windows-rs#1985 (comment)
The text was updated successfully, but these errors were encountered: