Genericize tracing interface

[sqfink]

Ideally, Zig internally should support multiple plugable tracing frameworks.

The current Zig tracing interface is exclusively targeted to https://github.com/wolfpld/tracy. There are a few other competing tracing frameworks, primarily https://github.com/opentracing, which provide similar functionality with slightly different semantics.

[daurnimator]

Isn't opentracing more focused around tracing remote procedure calls rather than in-process?

[andrewrk]

current Zig tracing interface is exclusively targeted to https://github.com/wolfpld/tracy.

To be clear, the current self-hosted compiler tracing interface is. There is no tracing interface in the standard library (yet).

Anyway, that said, I agree, this is one of those things that would be nice for the standard library to standardize on. I think we could do it similarly to how std.log works. Idea being, you could leave the trace calls in your code, and they will end up as no-ops unless activated by overriding the default tracing function.

Should we also do this for emulation/virtualisation? Special-casing Wine and QEMU seems like a suboptimal solution.

[nektro]

OpenTracing is now https://opentelemetry.io/

Spec: https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/overview.md
Go Client: https://pkg.go.dev/go.opentelemetry.io/otel/api@v0.12.0
Example: https://github.com/open-telemetry/opentelemetry-go/blob/master/example/basic/main.go