Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@yutannihilation
Copy link
Contributor

This is another part of an attempt to fix duckdb/extension-template-rs#15.

The idea is the same; set a reasonable default value if no envvar is specified in order to avoid rust-analyzer crash. However, I don't come up with what value is the "reasonable default value." Probably, it can be the same as the version of libduckdb-sys, but I couldn't find nice way to acquire the value programmatically.

I also believe the value provided by extension-ci-tools, "v0.0.1", is not quite right for Rust case. As it uses the C extension API, which was officially introduced in DuckDB v1.2.0, maybe this should be "v1.2.0" unless the C extension API introduces some breaking change...?

https://github.com/duckdb/extension-ci-tools/blob/00e6af068429bf776a54f67cb1cd1ff5370a8dd7/makefiles/c_api_extensions/base.Makefile#L39-L42

@Maxxen Maxxen merged commit 79417fb into duckdb:main Apr 9, 2025
4 checks passed
@Maxxen
Copy link
Member

Maxxen commented Apr 9, 2025

Thanks!

@yutannihilation yutannihilation deleted the set-default-ver branch April 9, 2025 10:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

rust-analyzer panicks on duckdb_entrypoint_c_api due to lack of the envvars

2 participants