On Fri, Jun 6, 2025, at 9:29 AM, Stan Marsh wrote: > I.e., yes, I get the theoretical reasons, but it generates confusion > for the user > > [...] > > Of course, > you still have to "enable" them in your script or shell in order to > actually use them.
Exactly, you have to explicitly opt into using them. So I fail to see how this hypothetical "confusion" manifests in practice. Being confused about a mailing list post that wasn't written as clearly as it could have been is not really relevant. (Your argument has some merit when it comes to non-loadable built-ins like "printf" and "test", but that ship sailed a very long time ago.) > the purpose of the example builtins is more for instruction than for > performance. Regardless of the intended purpose, I know for a fact that some people use them to speed up loops and such. (Arguably they should try to avoid such bottlenecks in the first place, but it is what it is.) -- vq
