-
-
Notifications
You must be signed in to change notification settings - Fork 970
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
Add a "benchmark" cmd to dotnet #213
Comments
Good idea, but as for me I don't have time now. |
An interesting post about the subj: https://surfingthecode.com/fun-with-global-tools-in-.net-core-2.1-preview/ |
The official documentation: https://docs.microsoft.com/en-us/dotnet/core/tools/global-tools |
I would like to do this. |
@CodeTherapist, great! |
@AndreyAkinshin, Done! At least a first version of it - let me know if that solves this issue. The tool supports the following syntax:
Btw. I'm little bit confused because the build is failing. |
@CodeTherapist this particular failure is not your fault, I am going to take a look into that failure to see what is going on |
Implemented in #1006 |
So it seems like you can add extra commands to the dotnet tooling, how cool would it be to be able to do
dotnet benchmark
?This could then interact with the
BenchmarkSwitcher
so you can do--class=Benchmarks
,--diagnosers=Memory
, etcFrom my understanding we would have to propose it as a CLI issue, but if we were serious about it, I think someone should do a proof-of-concept first.
Anyone agree? Anyone want to take it on?
The text was updated successfully, but these errors were encountered: