Re: [PATCH v1] string.h: Unconditionally expose C23 functions

[Thorsten Glaser <tg@mirbsd.de>]

On Fri, 11 Jul 2025, Rich Felker wrote:

>However in this case, the namespace str* and mem* was already reserved,
>so I think even without that policy, there's no reason not to expose
>them unconditionally unless we're using strictness to expose
>non-conforming application-side expectations.

Given there seems to be *no* tool in existence that can take a
C codebase and check it for use of reserved identifiers, like
is + lowercase, that is, no accessible way for people to avoid
accidentally using “reserved” identifiers, I’d ask to at least
consider it a little longer given you have actual user reports
that they have to patch out things like this downstream.

bye,
//mirabilos
-- 
“It is inappropriate to require that a time represented as
 seconds since the Epoch precisely represent the number of
 seconds between the referenced time and the Epoch.”
	-- IEEE Std 1003.1b-1993 (POSIX) Section B.2.2.2