Open TIHan opened 1 month ago
Tagging subscribers to this area: @dotnet/area-system-runtime-intrinsics See info in area-owners.md if you want to be subscribed.
I recommend doing this after making the files alphabetical in https://github.com/dotnet/runtime/issues/104834
priority:2 for RC1 snap : User visible API
This is more rather priority 3, or could even be pushed out to .NET 10.
Marking an API as unsafe
has no impact to the public signature, it simply allows the internal implementation to use pointers and the public signature to contain pointers. It's then only if the public signature contains pointers that the downstream consumers must also themselves use unsafe
.
In many cases we've just marked the entire class as unsafe
to simplify long term revisions/changes to known lowlevel code.
Pushing out to .NET 10 because we have many issues for RC1 snap.
Because we have been copying and pasting from the generated code for SVE, the generation always marked the APIs as
unsafe
. We need to removeunsafe
from them if the API does not use any pointers.Relevant files: