On Fri, 28 Jul 2023 at 21:57, Daniel Henrique Barboza <danielhb...@gmail.com> wrote: > Here's some trivial changes following Peter's call to arms against > free() and friends in gitlab issue #1798 in an attempt to enforce > our memory management guidelines [1].
To clarify, this isn't a "call to arms". The issue is marked up as a "bite-sized task", which is to say that it's a potential easy place to start for newcomers to the community who might be making their first contribution to the codebase. The changes it suggests aren't urgent; at most they're a nice-to-have, since glib guarantees that you can mix malloc/free and g_malloc/g_free. We've had this sitting around as a suggestion on the wiki page for bite-sized-tasks for years, and occasionally people come through and have a go at it. I wanted to clean up and expand on the description of what we had in mind for the change, to give those people a better chance of successfully completing the task. thanks -- PMM
