namespace protect or symbol mangle for other built-in libs
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 248
- Forks
- 72
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 15
Description
follow up from https://github.com/LLNL/conduit/pull/743, where we resolved an issue where conduit symbols for rapidjson conflicted with another lib using rapidjson. (The fix was to use a custom namespace)
We may want to proactively apply either a custom namespace or mangle functions for other builtin libs:
- libb64
- libyaml
- civetweb
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 pull request #743 to understand how the RapidJSON namespace conflict was resolved. Then inspect how the bundled libb64, libyaml, and civetweb libraries are integrated and determine whether custom namespaces or symbol mangling can be applied consistently. Done means the listed libraries no longer expose conflicting symbols.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100