Dylan Perks
Dylan Perks
Trimming is more suited for the end consumer (application) instead of libraries, as you don't want to prematurely trim away IL for it to blow up on the downstream consumer.
I am not open to any trimming operations being done to Silk.NET itself. However, if we needed to annotate some APIs for the new (experimental) trimmer then this should be...
Primarily because as of 2.0 Silk.NET is still a .NET Standard library, and the new trimmer is .NET 5 only.
Not for something like this, as it'll be large-scale and files will get messy with lots of preprocessor directives.
Apparently auto trimming is cool, see this tweet from Tanner https://twitter.com/tannergooding/status/1412124486539702272?s=20
Bringing this back for this year's Hacktoberfest as well. This doesn't require much foreknowledge of Silk.NET's internals - this issue is mostly for building a C# API similar to Assimp's...
Also yes I am opening issues regarding code that isn't even written yet.
Now there are!
We'll be happy to accept this if you're still willing to contribute it! I notice there hasn't been any commits yet.
Has there been any update on this? @HurricanKai this has been open for a while, how much do you care about the unit testing?