Open JonDouglas opened 1 year ago
For what it is worth, I reached out to folks on the Native AOT team. There isn't an easy way to detect this today and would be fairly involved. In other words, there isn't a tool to validate/automate this today that could be used for badging purposes.
While we may be able to detect something like <IsAotCompatible>
, an author could ignore and publish a package anyway.
I think labeling by the author would be enough, it may not be a validated promise, but maybe that flag could produce the same warnings as PublishAot for the author. And if the library is not compatible even though the flag/badge says so it is just a bug in the library like any other.
that would indeed be great!
Related Problem
No response
The Elevator Pitch
It would be cool to provide some type of metadata associated with a .NET library that supports the Native AOT functionality.
https://devblogs.microsoft.com/dotnet/creating-aot-compatible-libraries/
We could show badges and provide filtering experiences for packages that are compatible with this functionality and consumers may want to use in their projects for the benefits they get from the feature.
Additional Context and Details
No response