slbotbm opened a new pull request, #2661: URL: https://github.com/apache/iggy/pull/2661
## Which issue does this PR close? <!-- We generally require a GitHub issue to be filed for all bug fixes and enhancements. You can link an issue to this PR using the GitHub syntax. For example `Closes #123` indicates that this PR will close issue #123. --> Closes #2100 ## Rationale <!-- Why is this change needed? If the issue explains it well, a one-liner is fine. --> This PR implements a blocking c++ client using CXX. I'll open a discussion on the design by the weekend. ## What changed? <!-- 2-4 sentences. Problem first (before), then solution (after). GOOD: "Messages were unavailable when background message_saver committed the journal and started async disk I/O before completion. Polling during this window found neither journal nor disk data. The fix freezes journal batches in the in-flight buffer before async persist." GOOD: "When many small messages accumulate in the journal, the flush passes thousands of IO vectors to writev(), exceeding IOV_MAX (1024 on Linux)." BAD: - Walls of text - "This PR adds..." (we can see the diff) --> Deletes the old incomplete client. Adds a client that uses cxx to generate rust -> cpp bindings. `examples/example.cpp` has been temporarily included to show how the public API would look like. instructions on running it are included in `README.md`. ## Local Execution - Passed - Pre-commit hooks ran <!-- You must run your code locally before submitting. "Relying on CI" is not acceptable - PRs from authors who haven't run the code will be closed. Did you have `prek` installed? It runs automatically on commit. See [CONTRIBUTING.md](https://github.com/apache/iggy/blob/master/CONTRIBUTING.md). If not installed, explain why (e.g., non-Rust changes only, small change). --> ## AI Usage <!-- If AI tools were used, please answer: 1. Which tools? (e.g., GitHub Copilot, Claude, ChatGPT) 2. Scope of usage? (e.g., autocomplete, generated functions, entire implementation) 3. How did you verify the generated code works correctly? 4. Can you explain every line of the code if asked? If no AI tools were used, write "None" or delete this section. --> 1. OpenAI Codex, Google Gemini 2. Writing code, and reviewing. I planned everything out and made the AI write the code. 3. Read through it multiple times and verified the output to the best of my abilities. 4. I can explain about 95% of the code. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
