-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support AOT tools in .NET tools #40931
Comments
IMO it's not that crazy. It would save lots of disk space on the nuget side of things (not to mention simplifying the solution for this github issue), and if you think about it, a user that installs a dotnet tool is in most cases a dev, so it's not too insane to require him to have some compiler tools to be able to have his tool optimized for speed. (Just my 2 cents) |
If a user installs a global tool by using an x86 .NET SDK on an x64 operating system, then would |
Tools of all kinds benefit from fast execution speeds, so compiling them for AOT makes sense. .NET Tools are a very easy way to distribute tools, so it would seem natural that tools be able to be AOT compiled. There are a few hurdles that would need to be cleared first, though:
Another, potentially more crazy idea might be to on-demand AOT a tool for the current platform on tool install. This could require data that we don't already have packaged in the tool, and might require dependencies like a C/C++ compiler that aren't part of our already-expressed dependency tree for the SDK.
The text was updated successfully, but these errors were encountered: