> If you meant that the function could possibly allocate fields of `result`, the API should always have a `free_result()`. Yea that's what I meant. But this so

> If you meant that the function could possibly allocate fields of `result`, the API should always have a `free_result()`. Yea that's what I meant. But this sort of gets into the weirdness of docs, if there is a `free_result` somewhere then authors should make sure to put a "see also free_result()" in their doc comments, especially when you don't have the niceties of constructors/destructors.