chore: drop benchmarks folder#3709
Merged
Merged
Conversation
Assisted-By: claude-sonnet-4-5
gtardif
approved these changes
Jul 17, 2026
docker-agent
left a comment
docker-agent
left a comment
Contributor
There was a problem hiding this comment.
🟢 No issues found — LGTM! View logs.
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
3 participants
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.
The
benchmarks/compactiondirectory contained a standalone benchmark harness — a separate Go module, a judge program, and a couple of Python helper scripts — that was added during early development. Nothing in the build references it: it is absent from theTaskfile, theDockerfile, and the main Go module.Removing it reduces repository noise and eliminates the maintenance burden of an unmaintained Go module with its own dependency tree.