RoaringBitmap / RoaringBitmap/CRoaring
Debug visualizer for Visual Studio or lldb
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.9k
- Forks
- 334
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 17
Description
We recently started using Roaring64Map in our code to manage a (potentially) large visited set for graph traversal. We replaced an unordered_set<uint64_t> and our simplest traversals are twice as fast for large graphs. Thanks to all who worked on it.
Our developers occasionally set breakpoints to look at results from a traversal, and want to know if a given node (integer) is in the result. With unordered_set<uint64_t> Visual Studio's debugger would show you a list of the entries in the hash table, which was convenient. I have been asked to create a visualizer for Visual Studio. Since I primarily use Linux/clang myself, I am also interested in doing one for lldb.
Obviously, it would be great to just find a ready-made one, but I'm willing to do the work. I'm mostly looking for tips or advice on how I might accomplish this task.
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 file, test, or entry point. Start by researching how Roaring64Map can be exposed through Visual Studio or lldb debugger visualizers. Done would be a working visualizer that lets developers inspect entries and check whether a node is present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100