On Thu, Dec 11, 2025 at 3:06 PM Gilles Sadowski <[email protected]> wrote: > > Hello.
> Isn't it a "chicken-and-egg" question? > Isn't the purpose of a "common" library to implement well-defined and > generally useful functionality, in the hope that it'll incite code reuse? > Until said functionality is implemented, it obviously cannot be used... No, it isn't. The use case comes first. If you can point to three existing projects that have had to implement this functionality already, and that would be willing to replace their existing code with a common library, then you have a case for implementing it here. Absent that, it is unlikely it will be adopted broadly enough to be worth the effort. -- Elliotte Rusty Harold [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
