codegen only used functions in duckdb C API

[myrrc]

Make duckdb-vortex compilation slightly faster

[codspeed-hq]

Merging this PR will not alter performance

⚠️ Unknown Walltime execution environment detected

Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.

For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.

⚠️ Different runtime environments detected

Some benchmarks with significant performance changes were compared across different runtime environments,
which may affect the accuracy of the results.

Open the report in CodSpeed to investigate

⚡ 3 improved benchmarks
❌ 3 regressed benchmarks
✅ 1575 untouched benchmarks
⏩ 3 skipped benchmarks¹

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
❌	Simulation	chunked_varbinview_canonical_into[(1000, 10)]	162.1 µs	198.6 µs	-18.39%
❌	Simulation	chunked_varbinview_into_canonical[(1000, 10)]	178.2 µs	214.7 µs	-17.01%
❌	Simulation	chunked_varbinview_canonical_into[(100, 100)]	274 µs	308.4 µs	-11.15%
⚡	Simulation	chunked_varbinview_opt_canonical_into[(1000, 10)]	214.7 µs	177.8 µs	+20.8%
⚡	Simulation	bitwise_not_vortex_buffer_mut[128]	215.3 ns	186.1 ns	+15.67%
⚡	Simulation	bitwise_not_vortex_buffer_mut[1024]	275.6 ns	246.4 ns	+11.84%

Tip

Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.

---

_{Comparing myrrc/duckdb-api-codegen (4955ddd) with develop (202953d)}

Footnotes

1. 3 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[0ax1]

How come these are dropped and why?

[myrrc]

We had had a double check: one in cbingden option, other in header/trailer. I've removed the hand-written one.

[0ax1]

The binary gets smaller but also all API is now hidden behind having to change the build.rs when not exposed explicitly.

[myrrc]

If you want to extend Rust API, you still likely need to look into duckdb.h/.hpp, and you need to write a Rust wrapper over Rust unsafe {} functions, so we're not losing anything here.

[0ax1]

Seems a bit tedious to maintain a custom list, but alright let's try this in practice.