Carlos Alberto Cortez

I totally agree with @yurishkuro opinion on the complexity part, and also think that as @adriancole says, having a no-op active `Span` (and related `Scope`) could help. (I think we...

Hey @rbtcollins Sorry for the long delayed ping. Wondering if we should discard these changes, now that we don't use `Continuation`s as part of the main API (we still have...

Sounds good to me, thanks! And definitely good motivation to finish the latest cycles in the compatibility section in OTel.

I agree on this - and as a matter of fact, the Python API has this (a Span has a reference to its Tracer). I'm wondering if there's some kind...

The code change is trivial, but Tracer writers must agree on this first (in case there's a reason or situation where they can't add this). @yurishkuro maybe can bring some...

Trying to get this one moving again, to not end up being stale - feedback requested from @felixbarny @CodingFabian Let us know ;)

@fzakaria Hey, thanks for the latest feedback. Would you mind proposing a PR so we can get this item going?

@tylerbenson Oh, I'm genuinely not sure this is something that could need to go in the actual `Specification` or be simply considered sugar on top. For example, `Tracer.activeSpan()` is a...

Hey @yurishkuro out of curiosity, would you envision also having `ScopeContext` without an actual active `Span`? ```java try (Scope scope = tracer.scopeManager.newScope().withValue("deadline", someDeadline)) { ScopeContext context = scope.context(); // opaque...

Hey @indrekj @pavolloffay @palazzem @tylerbenson @tedsuo I've updated the document with minor corrections and updating it based on the latest OT Java iteration (making some operations optional). Let me know.