https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113835
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Should we really be reaching the limits for cases like this? I mean, all the default ctors produce the same value here and we could figure out that they are in no way dependent on the exact position of the element in the vector, nor allocating heap memory during constexpr evaluation, so ideally we'd optimize and just fill in the whole initializer with the same value (ideally using range for the ctor index to even save compile time memory). Guess the hard part is find out the cases where the constexpr evaluation for element would be dependent on something that would prevent such an optimization.
