Tanner Gooding

The intent of the xml docs linked is basic intellisense. Users wanting more comprehensive information should refer to the official documentation

It is out of scope for a bindings library, especially one providing bindings over much of the Windows SDK, to provide documentation or examples for things which even the underlying...

Computer math != real math, it is a looser approximation that has to account for operating in a finite/bounded domain. There are various things about it that don't line up...

There's always a balance around these in getting the docs to be familiar to people from different domains. Contributions to improve the docs are welcome.

In general for any page you simply need to click the `edit this document` button and it will take you to the relevant markdown file:  You may also consider...

CC. @JulieLeeMSFT, @jeffhandley Also CC. @davidwrighton for CG2/R2R considerations and @AndyAyersMS for PGO considerations CC. @BruceForstall and @dakersnar who are part of the working group

> I've been having a look through the existing Vector APIs and it looks like Vector is only partially implemented for hardware acceleration, or am I misunderstanding? If I've not...

> For instance, when AVX-512 is supported but an operation isn't supported natively, then the fallback path still needs to treat Vector as a 512-bit vector? Correct. `Vector` currently has...

We'll ultimately need something that works reasonably well across a range of hardware. That includes `x64`, `Arm64`, `Wasm`, and future platforms. Such support needs to account for both older hardware...

I do not. At a glance this looks like it might have already been resolved via https://github.com/dotnet/runtime/issues/75606