h_benchmark_result_free
Right now, h_benchmark
results leak. Something named like the title would fix that. Some other approach would probably also be okay. Maybe if you passed the result function as a callback to h_benchmark?
Right now, h_benchmark
results leak. Something named like the title would fix that. Some other approach would probably also be okay. Maybe if you passed the result function as a callback to h_benchmark?