Idiomatic way to distinguish two zero-arg constructors

Question

I have a class like this:

struct event_counts {     uint64_t counts[MAX_COUNTERS];      event_counts() : counts{} {}      // more stuff  };  

Usually I want to default (zero) initialize the counts array as shown.

At selected locations identified by profiling, however, I'd like to suppress the array initialization, because I know the array is about to be overwritten, but the compiler isn't smart enough to figure it out.

What's an idiomatic and efficient way to create such a "secondary" zero-arg constructor?

Currently, I'm using a tag class uninit_tag which is passed as a dummy argument, like so:

struct uninit_tag{};  struct event_counts {     uint64_t counts[MAX_COUNTERS];      event_counts() : counts{} {}      event_counts(uninit_tag) {}      // more stuff  }; 

Then I call the no-init constructor like event_counts c(uninit_tag{}); when I want to suppress construction.

I'm open to solutions that don't involve the creation of a dummy class, or are more efficient in some way, etc.

Answer 1

The solution you already have is correct, and is exactly what I'd want to see if I were reviewing your code. It is as efficient as possible, clear and concise.