Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
Well, it's something that serves for memory deallocation in ctags which is about all I know. But this simply is an upstream code (and it fixes the leak for me, I tested it) and as long as we trust upstream, it should be OK to use.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.