Maybe send a PR to BH instead ...
Open
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 1.1k
- Forks
- 266
- Avg merge
- 2h 56m
- Merged PRs (30d)
- 1
Description
... of using a poetically named path?
BH is not exactly a closed system as even a casual perusal of its NEWS.Rd file will tell you. [ Apologies for the unrendered Rd file; the version of NEWS.Rd on CRAN missed the last update. ]
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
Review rstan/rstan/inst/include/boost_not_in_BH/boost and the BH NEWS.Rd file first. Determine which dependency content is being maintained in the poetically named path and what a corresponding BH change would need to cover. Done means the dependency is handled through BH rather than an unresolved parallel path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100