@WG-prioritization issue #68010 has been requested for prioritization.
Afaict there isn't really a reason to use this and it was undetected for 10 version,
Mhh, I think it's worth bisecting a bit
Can we profile the compiler to see where that additional comilation time comes from?
Did some bisection, this seems like a const-eval bug. I pinged RalfJung on the issue
Depending on his answer I think we can assign
Okay so this is interning walking every single field of that array... and taking forever to do that, obviously.
So the problem comes from the big size of the array. I think this means we can tag
1.31.0 is the introduction of const evaluation, right? So this isn't much of a regression, but rather a cost induced by const evaluation.
@LeSeulArtichaut do you want to go ahead and tag
P-low and remove
Issue #68010's prioritization request has been removed.