Rename AbstractSpan
to Span
for consistent access to static methods
#824
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Unifies access to static interface methods. Other API interfaces with static methods have a class without the
Interface
suffix that provides an implementation, e.g.:Baggage::getCurrent(): BaggageInterface
SpanContext::getInvalid(): SpanContextInterface
I considered creating a
Span
class that does not implementSpanInterface
but disliked the idea of splitting the PHPDoc documentation in different classes.