Currently, different implementations decide, on Span creation, whether to set it as the active/current instance or not (in Java startSpan() does not, but in Python start_span() does, for example).
I feel like there should be a clarification or recommendation for every language, mentioning the default Start Span operation does not set the active/current instance, and optionally offer an Start Span + activate operation*. This would give us some homogeneity.
If this makes sense, I'll open up a RFC. Opinions?
(In OT, we had two operations for this actually, namely Start Span and Start Active Span).
[1] In Java we cannot offer an Start + Activate method as it becomes hard to properly handle/report errors. See opentracing/opentracing-java#291
Currently, different implementations decide, on
Spancreation, whether to set it as the active/current instance or not (in JavastartSpan()does not, but in Pythonstart_span()does, for example).I feel like there should be a clarification or recommendation for every language, mentioning the default Start Span operation does not set the active/current instance, and optionally offer an Start Span + activate operation*. This would give us some homogeneity.
If this makes sense, I'll open up a RFC. Opinions?
(In OT, we had two operations for this actually, namely Start Span and Start Active Span).
[1] In Java we cannot offer an Start + Activate method as it becomes hard to properly handle/report errors. See opentracing/opentracing-java#291