From 65bab0d3c1e0fae8ea6bdb8b25d698ffff705e73 Mon Sep 17 00:00:00 2001 From: floor-licker Date: Fri, 30 Jan 2026 21:30:10 -0500 Subject: [PATCH] docs: update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 197c5e2..5fa38be 100644 --- a/README.md +++ b/README.md @@ -8,7 +8,7 @@ A high-performance drop-in replacement for `polymarket-rs-client` with latency-o At the time that this project was started, `polymarket-rs-client` was a Polymarket Rust Client with a few GitHub stars, but which seemed to be unmaintained. I took on the task of creating a Rust client which could beat the benchmarks quoted in the README.md of that project, with the added constraint of also maintaining zero alloc hot paths. -I also want to take a moment to clarify what zero-alloc means because I've now recieved double digit messages about this on twitter/x and telegram. In general, zero alloc means either zero alloc in hot paths (which can be a bit more arbitrary) or atlernatively it can mean zero alloc ater init/warm-up, which is the objective of this repository. Succinctly that means that **the per-message handling loop never touches the heap**. +I also want to take a moment to clarify what zero-alloc means because I've now recieved double digit messages about this on twitter/x and telegram. In general, zero alloc means either zero alloc in hot paths (which can be a bit more arbitrary) or atlernatively it can mean zero alloc after init/warm-up, which is the objective of this repository. Succinctly that means that **the per-message handling loop never touches the heap**. Notably order book paths that introduce new allocations by design: - First time seeing a token/book (HashMap insert + key clone): `src/book.rs:~788`