tursodatabase / tursodatabase/libsql
Async runtime assumption for libsql rust
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
I noticed that libsql's API is async.
Does it bind to the tokio runtime? And do we have some sync version; for example, the memory db should be good to run in sync?
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 libsql's Rust API and how its async operations use the Tokio runtime, then inspect the in-memory database path. Determine whether a synchronous API is supported or feasible; done means clearly documenting the runtime requirement or defining the scope of a sync version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, sqlite
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100