awful one liners don't improve readability or performance

Open
#6,995 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
c

Research direction

Start with the three referenced locations in src/fread.c at lines 1259, 1811, and 2512, then search nearby code for similar one-line control-flow statements. Separate increment operations from control flow where applicable, preserve behavior, and run the project's relevant tests to confirm the parser still works.

Written by the indexing model from the issue text.

Description

code-quality internals

This is a pattern I've seen in various places in the code. Collapsing everything into one line doesn't make the code run faster, the compiler is smart enough to sort it out.

examples:

https://github.com/Rdatatable/data.table/blob/f032d6682b87c97e24acbb3b7e40a96626b46c67/src/fread.c#L1259
https://github.com/Rdatatable/data.table/blob/f032d6682b87c97e24acbb3b7e40a96626b46c67/src/fread.c#L1811
https://github.com/Rdatatable/data.table/blob/f032d6682b87c97e24acbb3b7e40a96626b46c67/src/fread.c#L2512

I think it's especially important to separate operations like the increment (++) operator away from control flow statements. Again, this doesn't cost any performance.

Dominant language
R
Stars
3.9k
Forks
1.1k
Avg merge
14h 4m
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Rdatatable/data.table

All issues in Rdatatable/data.table

Similar issues

More R issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.