Is there any appetite for making some of the shared C# libraries, such as EpicGames.Core or EpicGames.Perforce, compatible with C# trimming?
The use case is that we sometimes build custom C# tools and have started using epic shared libraries as a dependency rather than having duplicate copies of similar logic. Depending on the deployment model, these tools might be published as standalone, in which case trimming can greatly reduce the footprint of that tool.
Primarily this would involve adding a few attributes to classes or methods, such as a DynamicDependencyAttribute https://learn.microsoft.com/en\-us/dotnet/api/system.diagnostics.codeanalysis.dynamicdependencyattribute?view\=net\-9\.0
If there’s interest in something like this, I can put together a PR to review and upstream. Just didnt want to go to the trouble if there’s no interest on the Epic side