protty
protty
The `COUNT_SHIFT` was incorrectly `0` when it should have been `1` to shift out the `QUEUED` bit. This led to the initial barrier count being treated as a `*const Waiter`...
In the [listen function](https://github.com/karlseguin/websocket.zig/blob/d71dcb04b3578398db72768a6ff8acf58cd551ed/websocket/listen.zig#L16), It starts the async frame for `client.handle` in a loop and binds it to a temporary variable `_`. Once `client.handle()` suspends (e.g. from partial socket read),...
The current event loop is not ready yet (relatively slow, windows unfinished, bugs/races) and many wish for it to be. From the discord communities at least, there seems to be...
Building off of #489, this changes `vsr.Client.Request` to be an intrusive node provided by the caller with the event data, eliminating the need to allocate and manage intermediary `Demux` nodes....
Implements TreeType using only Keys instead of Values. This fuzzes the expected usecase of Manifest without Grid/Storage plumbing. It also gives TreeType and CompactionType a simpler model to compare against.
Enables `ReadFile` and `WriteFile` to use Overlapped IO instead of being synchronous. A "why not" idea given io_uring. Doesn't seem to affect performance (similar to async file IO on macos...
Currently crashes in `tb_client_init` on windows during test. ## Pre-merge checklist Performance: * [x] I am very sure this PR could not affect performance.
We currently open the database file with `O_DSYNC` (along with `O_DIRECT`) which makes all writes ensure the data (not file metadata) is flushed to disk before completing. While this is...
Currently, a `tb_client` user requests how many packets they want when creating a client instance. To submit a request, the user acquires a packet from the client and releases it...
First step to making tb_client packets intrusive is having each packet map 1:1 to a `vsr.Client.Request`. This was awkward to do as `vsr.Client` is specific to `StateMachine` and holds a...