docs: fix malformed benchmark throughput table
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 90/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- markdown
- Domain
- documentation
Research direction
Open docs/benchmarks.md and inspect the x86_64 throughput table around line 110. Compare its header with the separator row, then check nearby benchmark tables for the same column-count issue. Done means the affected separator rows match their headers and the Markdown tables render without an extra column.
Written by the indexing model from the issue text.
Description
Problem
In docs/benchmarks.md, the x86_64 throughput table has a column-count mismatch.
At the table starting around line 110, the header defines 7 columns:
| Scenario | Size | cjson | simdjson | `qjson.parse` | `qjson.decode + access content` | `qjson.decode + qjson.encode` |
But the separator row defines 8 columns:
|---|---|---:|---:|---:|---:|---:|---:|
This can render the Markdown table with an extra empty column or otherwise malformed alignment.
Expected fix
Remove the extra trailing separator cell so the separator row has 7 columns, matching the header.
It is also worth checking nearby benchmark tables for the same issue.
- Dominant language
- Rust
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from api7/lua-qjson
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 30/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gitbutlerapp/gitbutler#15998 · 1 comment ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100