RoaringBitmap / RoaringBitmap/roaring
RFE: Makefile or equivalent
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.9k
- Forks
- 262
- Avg merge
- 2h 34m
- Merged PRs (30d)
- 8
Description
Any objection to adding a Makefile or equivalent that covers common tasks? It would be opt-in.
The other Roaring projects don't seem to have this so maybe there is a cultural objection.
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
The issue names no files, tests, or entry points. First review the repository to identify its common development tasks and any existing build conventions, then define an opt-in Makefile or equivalent that covers those tasks without conflicting with the project's stated conventions; done means the proposed interface and scope are agreed upon.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100