Remove the in-repo benchmark: the family's benchmark is schema's data-driven bench - #2
Merged
Merged
Conversation
…-driven bench Per mas-bandwidth/schema#196. Deletes bench/serialize/bench/Bench.java, the Makefile bench target and its variables, and the README benchmark section with its pasted numbers. Deletion not archival: a dormant bench is a re-activation and drift surface, and git history is the archive. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Per mas-bandwidth/schema#196 (owner ruling, 2026-08-31), every serialize-family repo's in-repo benchmark is deleted.
The family's benchmark is now schema's data-driven bench: one variant corpus driven through the real generated codecs in all nine languages. A per-repo bench that nobody runs is a re-activation-and-drift surface — it will come back to life some future day carrying stale methodology and stale numbers. Deletion, not archival: git history is the archive. If the generated-vs-hand-written comparison is ever wanted again, it is remeasured deliberately from scratch, never revived from dormant code.
Pure deletions. Correctness tests, conformance and golden vectors, fuzz corpora and example programs are untouched; the full suite is green.
🤖 Generated with Claude Code