pub fn built_against_version() -> Option<&'static str>Expand description
The DuckDB release this extension declares it was built against, if any.
Set QUACK_RS_TARGET_DUCKDB_VERSION when building — to the exact release
whose headers libduckdb-sys resolved to, e.g. v1.5.5. check then
short-circuits to AbiCheck::Compatible whenever it equals the running
engine’s version, without needing that release in expected_slot_count’s
table.
This is what keeps an extension working across a DuckDB release. When
DuckDB ships a new version, the community-extensions repository rebuilds
every extension from its current source and publishes a per-release artifact,
so users get a binary compiled against the new headers. That binary is
correct — but without a declaration, check can only see an engine version
this build of quack-rs has no verified layout for, and refuses it. The
declaration closes that gap without waiting for a quack-rs release.
The value is an assertion by the build, not a proof. check cross-checks it
against expected_slot_count when the declared release is a known one and
reports AbiCheck::DeclaredVersionMismatch if they disagree.