Skip to content

RegisterAggregator requires "trace" build tag? #433

Closed
@ghost

Description

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!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions