Date: Mon, 20 Apr 2026 15:10:15 +0200
On 4/20/26 12:44, Muneem via Std-Proposals wrote:
> The issue with creating on the fly is that it's painfully slow, like to
> get O(1) performance, you need some book keeping information. To get
I am not sure where you imagine this on-the-fly stuff occurs. The
solutions I have presented build a compile-time look-up table. This
table does not need to be a member of the tuple.
This, like many of your arguments, focus on premature optimization.
Consider the following implementation:
https://godbolt.org/z/n47qveWcM
Notices how the compiler has no problem optimizing this code even at
the lowest optimization level.
I do not know how to put this nicely, but these discussions feel more
like mentoring than standardization.
> The issue with creating on the fly is that it's painfully slow, like to
> get O(1) performance, you need some book keeping information. To get
I am not sure where you imagine this on-the-fly stuff occurs. The
solutions I have presented build a compile-time look-up table. This
table does not need to be a member of the tuple.
This, like many of your arguments, focus on premature optimization.
Consider the following implementation:
https://godbolt.org/z/n47qveWcM
Notices how the compiler has no problem optimizing this code even at
the lowest optimization level.
I do not know how to put this nicely, but these discussions feel more
like mentoring than standardization.
Received on 2026-04-20 13:10:19
