LGTM

LGTM

Seems this would make the tracing macros unavailable to native module authors, which I don't think is what we want at least long term. Would it be better to bundle the header?

/cc @nodejs/diagnostics

@joshgav I think it would be a good idea to hold off on encouraging native module authors to use these macros directly. Many of the macros are "implementation details" of other macros and not intended to be used outside the file. We should provide a simplified API for recording trace events or provide documentation on the set of macros intended to be part of the public API.

@Qard @matthewloring

We should provide a simplified API

expose a friendlier API to userland in the future

Makes sense and I agree in principal, although in the discussion at the last Collab Summit we said we wouldn't wrap the macros or provide an alternate C/C++ API.

or provide documentation on the set of macros intended to be part of the public API.

I would also be fine with this approach. Wrapping will incur some performance overhead which we could avoid.

My only issue with leaving it publicly accessible is that people may try to use it in ways not intended or expected. The _headers issue is a good example of that behaviour. Probably not as problematic as _headers was as this is native and in a less popular component, but we should at least have a plan for how to deal with userland exposure, intentional or otherwise.