Is there any concern that switching between ref / out and raw pointers might confuse callers as to which variables they're required to zero-init and which variables the callee will zero-init?

Is there any concern that switching between ref / out and raw pointers might confuse callers as to which variables they're required to zero-init and which variables the callee will zero-init?

@GrabYourPitchforks Aren't all locals zero-init right now? I didn't see any uses of the SkipLocalsInitAttribute.

@AaronRobinsonMSFT Nearly all libraries auto-compile with SkipLocalsInit injected by the build process.

SkipLocalsInitAttribute is set globally for the whole repo.

I am not particularly worried about the changes in this PR. THe blast radius is minimal (just affect immediate wrappers that deal with other interop intricacies), and some of the changes look like a geneneral improvement:

• NtCreateFile had a mix of raw pointers and out/ref already. It makes sense to use all raw pointers for consitency.
• out annotation was not quite correct on GetWindowThreadProcessId due to https://github.com/dotnet/runtime/pull/54370/files#diff-62e7105b6afe4f31872e90f2a84671553525312b7cf8e7a6d83b74556bff624aR53

Nearly all libraries auto-compile with SkipLocalsInit injected by the build process.

Didn't know that - thanks.