-
-
Notifications
You must be signed in to change notification settings - Fork 958
-
-
Notifications
You must be signed in to change notification settings - Fork 958
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
Implement ColoredLogger for LinqPad #447
Labels
Milestone
Comments
As an avid BDN and LINQPad user, I'm interested in implementing this (for Hacktoberfest). My understanding of the requirements is:
Out-of-scope (unless easy):
Without objection, I'll start working on this. |
Hey @bgrainger! The plan looks good to me. |
bgrainger
added a commit
to bgrainger/BenchmarkDotNet
that referenced
this issue
Oct 10, 2018
Merged
bgrainger
added a commit
to bgrainger/BenchmarkDotNet
that referenced
this issue
Oct 10, 2018
bgrainger
added a commit
to bgrainger/BenchmarkDotNet
that referenced
this issue
Oct 10, 2018
bgrainger
added a commit
to bgrainger/BenchmarkDotNet
that referenced
this issue
Oct 11, 2018
bgrainger
added a commit
to bgrainger/BenchmarkDotNet
that referenced
this issue
Oct 11, 2018
bgrainger
added a commit
to bgrainger/BenchmarkDotNet
that referenced
this issue
Oct 11, 2018
bgrainger
added a commit
to bgrainger/BenchmarkDotNet
that referenced
this issue
Oct 13, 2018
AndreyAkinshin
pushed a commit
that referenced
this issue
Oct 14, 2018
Adds a logger that sends coloured output to LINQPad, fixing #447. This new logger is enabled by default (in `DefaultConfig`) if the benchmark detects that it's being run under LINQPad. This makes it really easy to use, but I wasn't sure if this "magic" was appropriate; let me know if you'd like it to be done a different way.
#903 implemented |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Original discussion: #445 (comment)
The text was updated successfully, but these errors were encountered: