Lines of code per second
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 67
- Forks
- 101
- PR merge metrics
- No merged PRs in 30d
Description
On the front page (https://vlang.io/) it says:
V compiles ≈110k (Clang backend) lines of code per second
(Intel i5-7500, SM0256L SSD, no optimization)
However when I try to reproduce this I get ≈40k LOC/s (i.e. ≈25s in total). Steps I made:
- downloaded tools/gen1m.v
- ran
v run gen1m.v > result.v - ran
time v result.v
System info:
- MacBook Pro 13" (2015) (Intel i5 2.9 GHz, SM0512G SSD)
- V v0.3.2 d3e4058
- Clang compiler
Would it be a good idea to change the phrasing to:
V compiles up to ≈110k (Clang backend) lines of code per second
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start at the front page at https://vlang.io/ and locate the quoted Clang backend performance claim. Update the wording to reflect the issue's proposed qualification, then verify the rendered page shows the revised text.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100