> I guess the module rename would make it obvious to anyone using the old > 'malloc' module that they now need to choose which semantics they want, > the simpler 'malloc-gnu' or the POSIX-compliant 'malloc-posix'.
Haven't we implicitly been assuming/providing malloc-gnu since day 1? Do we really need to force all gnulib users ('cause pretty much everyone needs malloc, after all) to educate themselves about the issue and make a choice? Can we just keep malloc as malloc-gnu?