On Wed, Nov 16, 2022 at 1:18 PM Paul Eggert <egg...@cs.ucla.edu> wrote: > ... > If Clang's threatened pickiness were of some real use elsewhere, it > might be justifiable for default Clang to break Autoconf. But so far we > haven't seen real-world uses that would justify this pickiness for > Autoconf's use of 'char memset_explicit(void);'.
This line of arguments is not persuasive. It is full of logical fallacies. Maybe the Autoconf folks should argue something along the lines of, "this is the _only_ way to do it because <...>." Jeff
