comment #3:

> If that's the issue, why not simply use xfree in your wrapped API?

Somehow I missed that when trying solutions while running tests for my bindings under valgrind, but anyway... thanks that works.

That's fair as that makes sense from a C perspective.

Giving a little content for my usage of bash and why this is necessary for me... I'm wrapping bash's C API in a rust library and have to call back into C to properly free objects.

In this case, the general free() provided by C obviously isn't provided by bash's API as that would be strange, but strvec_dispose() is which can be used if this patch is applied.

While trying to use the list of all `set` and `shopt` options externally, I noticed shopt uses savestring() and thus can be freed via strvec_dispose() while set does not even through the functions are quite similar.

I think it makes sense to handle both of these the same way so the attached patch adds savestring() calls for `set` options as well.