Yurii Rashkovskii
Yurii Rashkovskii
Graduated the feature in #103. Still tracking as the feature gate hasn't been dropped, simply moved to `default`.
I suggest keeping this feature-gated until we see what the future compilation technique will bring in in terms of scoping. Thoughts?
I am currently attempting an extraction of an internal K/V interface here: https://github.com/yrashk/PumpkinDB/tree/kv
Another solution is to transmute lifetimes and do "transaction exit" scans, but that's pretty hacky.
Another solution is to introduce the concept of "linked Envs" where an Env can have a parent Env, effectively separating them by lifetimes.
Here's a thought. Based on my recent work on the [SPDK binding](https://github.com/PumpkinDB/rust-spdk), we can kind of forego this whole zero-copy issue. How so? SPDK allows to communicate with the NVMe...
The project is on hiatus right now. It was a little bit more of a rabbit hole that I anticipated and some original design decisions were less that optimal. That...
@stuarth looks like UUID/V1 can be covered with https://crates.io/crates/uuid_v1
Good stuff!
I absolutely agree, index retirement is one of the most difficult concerns here.