There may be a very good reason for this, for example gating the use of reflect behind a tag, but I was confused to discover that RegisterAggregator was not a default feature when I found it in one of the examples.
The line is here, and I can only get the custom_func example to build with go build -tags trace.
That's fine, if documented more clearly. But, does including -tags trace install performance-degrading hooks elsewhere? Is there a disadvantage to enabling the trace flag?
Thanks!
There may be a very good reason for this, for example gating the use of
reflectbehind a tag, but I was confused to discover thatRegisterAggregatorwas not a default feature when I found it in one of the examples.The line is here, and I can only get the
custom_funcexample to build withgo build -tags trace.That's fine, if documented more clearly. But, does including
-tags traceinstall performance-degrading hooks elsewhere? Is there a disadvantage to enabling thetraceflag?Thanks!