Motivation:
The TracerProtocol naming was annoyingly problematic and turns out we can and should actually move the withSpan APIs as top level functions which is typical Swift practice for such "global functionality".
This way we can withSpan() {} with less noise, and also gain back the Tracer protocol name.
Motivation: The TracerProtocol naming was annoyingly problematic and turns out we can and should actually move the withSpan APIs as top level functions which is typical Swift practice for such "global functionality".
This way we can
withSpan() {}
with less noise, and also gain back the Tracer protocol name.resolves https://github.com/apple/swift-distributed-tracing/issues/109