[Codestyle] Use of spaces around operators
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
The issue names no files, tests, formatter, or project-wide style configuration to inspect. First review the repository's existing C++ formatting conventions and determine whether the proposal has maintainer agreement; done would require an agreed scope and documented or applied operator-spacing changes.
Written by the indexing model from the issue text.
Description
I know codestyle is highly subjective, but I'd like to make a suggestion:
Would you mind adopting a codestyle with spaces around operators?
Without those it looks like a token soup that is hard to parse visually for me.
E.g.:
for(std::size_t i=0;i<k/8;++i){x?1+constexpr_bit_width(x>>1):0;x|=Block(1)<<(h&mask);
could be:
for(std::size_t i = 0; i < k / 8; ++i){x ? 1 + constexpr_bit_width(x >> 1) : 0;x |= Block(1) << (h&mask);
Or at least for "delimiters"
for(std::size_t i=0; i<k/8; ++i){x ? 1+constexpr_bit_width(x>>1) : 0;x |= Block(1)<<(h&mask);
To me this makes it much easier to see which parts belong together and not miss e.g. the "?", "|" or ";"
- Dominant language
- C++
- Stars
- 37
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
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.
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NVIDIA/cuda-samples#453 ·