Suggestion: perhaps re-arrange the OpenMP install options for macOS, putting `gfortran` as option 1, `llvm` as option 4?
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- r
- Domain
- documentation
Research direction
Open the data.table wiki's Installation page and inspect Step 2 of the "OpenMP enabled compiler for Mac" section. Review the existing compiler options and the context from issue #4899, then clarify the preferred ordering before editing. Done means the macOS install instructions present the agreed compiler choice first and accurately explain the options.
Written by the indexing model from the issue text.
Description
Recommendation in the macOS install docs
Perhaps move the gfortran up to option 1, perhaps llvm towards the bottom. Or whichever compiler is often used by those who develop the package towards the top. (This would be Step 2 of the "OpenMP enabled compiler for Mac" section). That way newbs like me are more likely to end up using the compilers most used by the experts. Defaults / order matters!
I'm a bit of a novice when it comes to compilers. Literally because the llvm option was first and appeared to work (or has historically), I tried that. Those "defaults" have stayed.
We're it not for my adventures outlined in #4899, I would not have know how much the compiler mattered. I just assumed if it successfully compiled an installed (no matter the compiler e.g. llvm vs gfortran) then things were fine.
That is not the case.
Could just be a fluke with the version of llvm I used. But woof, what a nightmare two days that was—and I almost lay the blame on data.table, my most favorite package!
- Dominant language
- R
- Stars
- 3.9k
- Forks
- 1.1k
- Avg merge
- 14h 4m
- Merged PRs (30d)
- 4
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 Rdatatable/data.table
-
as.data.table() recurses without end on a survival::Surv object (or any data.frame carrying one) Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Rdatatable/data.table#7887 ·
-
consistency tests
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Rdatatable/data.table#7853 · 3 comments ·
-
internals
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Rdatatable/data.table#6938 · 1 comment ·
-
encoding fread
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Rdatatable/data.table#5179 · 8 comments ·
-
documentation programming
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Rdatatable/data.table#3199 · 3 comments ·
All issues in Rdatatable/data.table
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
r-lib/pkgdepends#485 · 3 comments ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
beginners blocker
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enviPathR OpenBuild Error Build OK Build Warning policies-accepted pre-review precheck-passed
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Bioconductor/BiocContributions#207 · 6 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
datacarpentry/semester-biology#1255 ·