No description
Reinout Meliesie
1f1eac6369
Turns out there is no async code that would benefit from being executed on e.g. a multithreaded Tokio executor. Image loading is already being run on GIO's threadpool, and async-sqlite already has its own thread on which the connection lives. We also cannot easily bypass the latter and do Rusqlite connection IO on a Tokio threadpool because Rusqlite connections are not Send. Overall the current implementation is already pretty optimal given that we're not exactly dealing with thousands of operations per second in this little app. |
||
|---|---|---|
| docs | ||
| src | ||
| .editorconfig | ||
| .gitignore | ||
| Cargo.lock | ||
| Cargo.toml | ||
| readme.md | ||
Zoödex
A completely local film and series cataloguing app. Built for Linux with Rust and GTK4.
