Hi
On 9/4/26 15:02, Larry Garfield wrote:
We stress over the performance impact of certain generics approaches, we spent
a lot of time thinking about performance implications for hooks, or PFA, or
pipes. stdlib functions should not be exempt from that consideration. They
should just be considered appropriately and in context.
Okay, let me spell out what was implied in my previous email:
Performance considerations are asymmetric. If something is too slow,
this is a problem and means that it can't ship. However this only
affects the specific implementation - it is entirely possible to build a
faster implementation of the feature in question based on the accepted
semantics. Though in some cases the semantics inhibit a faster
implementation - or make it hard to create one. These considerations
obviously also apply to the stdlib functionality and not just language
features.
On the other side we would not ship something just because it’s fast.
And that is also independent of whether it’s stdlib or a language
feature (such as erased generics, which are fast, but have language
design arguments against).
Or in short: Performance is a property of the implementation, not a
property of the feature.
Best regards
Tim Düsterhus
