tursodatabase / tursodatabase/libsql
Include pre-compiled static libraries in the Go bindings
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
Let's do what DuckDB does and pre-compile static libraries of libsql in the repository and make cgo link to them:
https://github.com/marcboeker/go-duckdb/tree/master
To do that, let's move Go bindings to a go-libsql-experimental repository.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing Go bindings and cgo integration, then compare the linked go-duckdb repository for its pre-compiled static-library approach. Clarify how libsql libraries would be built and distributed and whether moving the bindings to go-libsql-experimental is required before implementation; done means the bindings link against repository-provided libraries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, go
- Domain
- build-system, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100