Add glossary terms for apple-specific C++'isms
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 110
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
Apple systems support dynamic libraries organized as `Frameworks`. Because this way of organizing C/C++ code is not cross platform we generally don't recommend or use `Framework`s at Mapbox. To clarify that apple systems support both dynamic and static libraries in the same way as other unix systems (and this is our preferred best practice) we should add `Frameworks` to the glossary to describe how they differ.
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.
Research direction
Locate the project's glossary and review nearby entries for terminology and scope. Add a Frameworks entry explaining how Apple frameworks differ from the dynamic and static libraries preferred at Mapbox; done means the glossary clearly covers the distinction and the existing guidance remains consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100