hinto-janai
hinto-janai
### About tracking issues Tracking issues are used to record the overall progress of implementation. They are also used as hubs connecting to other relevant issues, e.g., bugs or open...
### What Closes https://github.com/Cuprate/cuprate/issues/236. This replaces the `OnceLock` + `fn`s that were used in a `LazyLock` type of way for the entire codebase. There's other `OnceLock`s remaining but they are...
### About tracking issues Tracking issues are used to record the overall progress of implementation. They are also used as hubs connecting to other relevant issues, e.g., bugs or open...
This issue will keep track of problems with `monerod` RPC routes/types. ## Undocumented endpoint These endpoints exist in code but are not documented on the [website](https://www.getmonero.org/resources/developer-guides/daemon-rpc.html). | Endpoint | Definition...
## What [Rust 1.80 stablized `LazyLock`](https://blog.rust-lang.org/2024/07/25/Rust-1.80.0.html#lazycell-and-lazylock). This can replace any `std::sync::OnceLock` + `fn` usage. ## Where Any place using `OnceLock` + `fn` for `LazyLock` behavior, e.g.: https://github.com/Cuprate/cuprate/blob/929d19c4508a84d886ece03009a6fcdc5edea5c2/helper/src/fs.rs#L86-L90 ## How Replace...
## What Rust 1.79 brought [inline `const` expressions](https://blog.rust-lang.org/2024/06/13/Rust-1.79.0.html#inline-const-expressions). These can be used to _conditionally_ make static assertions (among other things). ## Why Turns runtime panics into compile time errors. ##...
### About tracking issues Tracking issues are used to record the overall progress of implementation. They are also used as hubs connecting to other relevant issues, e.g., bugs or open...
## What Currently, `cuprate_database`'s backend can be changed by _compiling_ it with different feature flags, i.e.: ```bash cargo build --features {heed,redb} ``` This issue is for discussing various methods `cuprate_database`...
### What Updates `cuprate-database`'s backends, no other changes. - heed: `0.20.0` -> `0.20.3` - redb: `2.1.0` -> `2.1.1` `heed` changes: - https://github.com/meilisearch/heed/releases/tag/v0.20.1 - https://github.com/meilisearch/heed/releases/tag/v0.20.2 - https://github.com/meilisearch/heed/releases/tag/v0.20.3 `redb` changes: - https://github.com/cberner/redb/releases/tag/v2.1.1
### About tracking issues Tracking issues are used to record the overall progress of implementation. They are also used as hubs connecting to other relevant issues, e.g., bugs or open...