Skip to content
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 more-explicit NewNop constructor #326

Merged
merged 1 commit into from
Feb 20, 2017
Merged

Add a more-explicit NewNop constructor #326

merged 1 commit into from
Feb 20, 2017

Conversation

akshayjshah
Copy link
Contributor

New already takes a variadic number of options, so we can't also take a
variadic number of cores. Instead, add a niladic NewNop constructor that
returns a no-op Logger.

This is already covered by tests, and is also backwards-compatible.

@sectioneight, this should fix one of your comments on the UberFX logging
upgrade PR.

`New` already takes a variadic number of options, so we can't also take a
variadic number of cores. Instead, add a niladic `NewNop` constructor that
returns a no-op Logger.

This is already covered by tests, and is also backwards-compatible.
@mention-bot
Copy link

@akshayjshah, thanks for your PR! By analyzing the history of the files in this pull request, we identified @jcorbin, @peter-edge and @skipor to be potential reviewers.

@akshayjshah akshayjshah changed the title Add a more-explicit NewNop Logger constructor Add a more-explicit NewNop constructor Feb 19, 2017
Copy link

@ascandella ascandella left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❤️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants