Tanner Gooding

It is not an `sbyte*` and has never been an `sbyte*`, it is an inline array of type `sbyte` which exactly matches the underlying Vulkan type definition. Previously it was...

This was also hit by other PRs, such as https://github.com/dotnet/runtime/pull/115117, see https://dev.azure.com/dnceng-public/public/_build/results?buildId=1036960&view=logs&j=67ac41de-1978-5f8d-a67a-2482e49b9998&t=94f6a79f-11ad-58cb-5d49-80afeb7fb21a

Static delegates are semi-related (both to the static lambda discussion above and to the static local functions here): https://github.com/dotnet/csharplang/blob/master/proposals/static-delegates.md

> the responsibilities of the caller don't change if the callee is sve or regular. There is a lot of nuance here and it is easy for developers to miss...

As per https://github.com/dotnet/ClangSharp/issues/571 you need to explicitly handle each header, namely by adding the right files to handle `um/mionidumpset.h` here: https://github.com/terrafx/terrafx.interop.windows/tree/main/generation/Windows/um

You shouldn’t exclude types like that. Typically whole headers are generated at once to avoid future breaks and potential issues

> Sadly in the case of this header the MINIDUMP_CALLBACK_INFORMATION generates something that does not look like it compiles because it generates this: What is causing it to fail to...

Also noting that `microsoft/cswin32` is driven off of `microsoft/win32metadata` which in turn builds its metadata using `dotnet/clangsharp` (which I maintain) + some post processing. TerraFX.Interop.Windows is just using `dotnet/clangsharp` and...

Using TerraFX.Interop.Windows in WPF probably isn't feasible (I had misunderstood and thought we were discussing a separate standalone thing); but pulling parts of it in from source or utilizing `dotnet/clangsharp`...

For reference: https://sharplab.io/#v2:EYLgtghgzgLgpgJwDQxASwDYB8ACAmARgFgAoHAZgAIBXAOyggDM5L9KBhSgb1Mr9ao4CANkppaMAFSUAsgApxMSgA8AlF0q9+2xdIiUAvJVgQAxgGsIGDAHtTYiQG1lAXQDcW7XxwB2ShA8SbQBfT00g/gpWEQcpWTlqRRV1cK9+XX9DYxgzS2s7WOd3MO1ff0CQsLCooVEM+VoktQ0S9Ik9LJMLK1t7RSKKtNY/ALDQiL5qwRj6uVpEiWSWia8M/SMuvN7C10G0stGV8e0p6LrFgDkFdv8kWOTDAD5/AaqVmpnL67iIO4WlNRPF67N6labnJRXNZ3RqLQEGZ4QV4rE7vcH3KE3X6UeZNVRApEglanWqFFyUADy30c5OxeKBtDgAHcdsViWizmTKdTaX96QicczWXtUpF0f1yVSJbccfznoyWf0iUNRd5xU5JTyZbi4fiBQrhaCxZykgAFLV03UE5GosEmxbm6XY/4PAWEtm242ks0WmFy4EeoYkz5KR0a7Uu+GI5HBIA== `int`, `uint`, `nint`, and `nuint` all work for `pointer` indexing, `array` creation, and `array` indexing. `uint`, `nint`, and `nuint` don't work for `stackalloc`. `uint` has always been...