-
Notifications
You must be signed in to change notification settings - Fork 858
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
Avoid usage of getSpanWithoutDefault when possible. #1690
Avoid usage of getSpanWithoutDefault when possible. #1690
Conversation
Signed-off-by: Bogdan Drutu <bogdandrutu@gmail.com>
9e4a283
to
57b1ce9
Compare
Codecov Report
@@ Coverage Diff @@
## master #1690 +/- ##
============================================
+ Coverage 85.36% 85.46% +0.10%
+ Complexity 1385 1383 -2
============================================
Files 164 164
Lines 5445 5435 -10
Branches 562 560 -2
============================================
- Hits 4648 4645 -3
+ Misses 590 587 -3
+ Partials 207 203 -4
Continue to review full report at Codecov.
|
It looks like there's only one usage left after this. Can we get rid of that one, as well, and get rid of the method altogether? |
@jkwatson you read my mind, but that one usage left is a bit different. I will followup on that soon. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was looking forward to this, thanks!
We check for
isValid
everywhere so this will not be a performance hit, explicitly because the DefaultSpan.getInvalid().getContext().isValid() will be memoized.