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

Optimizing calls to ResolveLogProvider() #140

merged 3 commits into from Oct 28, 2017


None yet
2 participants
Copy link

commented Jul 31, 2017

There is no reason to perform the computation in ResolveLogProvider more than once. In this pull request, I cache the result of the computation of ResolveLogProvider using the Lazy<> class. If someone really wants to call this method again, he can call the internal variant named ForceResolveLogProvider.

See also this issue.

@damianh damianh merged commit a4b58e3 into damianh:master Oct 28, 2017

1 check passed

continuous-integration/appveyor/pr AppVeyor build succeeded
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.