Use an enum for 'opt' in forderLazy

Open
#6,253 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Locate the forderLazy implementation and its related tests, then compare the existing opt comment with how the tests interpret its values. The work is done when opt uses an enum, verbose output can convert that enum to a string, and the tests explain the option meanings without cross-referencing source.

Written by the indexing model from the issue text.

Description

internals
          This comment is nice, but the tests are still very hard to understand without referencing back+forth the source code here. WDYT about using an `enum` instead? (including a method to convert `enum`->string for `verbose` printing)

Originally posted by @MichaelChirico in https://github.com/Rdatatable/data.table/pull/4386#discussion_r1525789093

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.