ilmanzo / ilmanzo/BinaryCoverage
when demangling c++ names, if resulting output is too long omit return type
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 9
- Forks
- 6
- Avg merge
- 1h 32m
- Merged PRs (30d)
- 11
Description
some demangled C++ names can get very verbose; if we demangle them with template parameters and so on, the risk is to see just the return type on the final report.
Let's get smarter and find out a compromise between completeness and usefulness in the html report; likely in case of very long symbols, the most interesting part to see is the class name and function name (and namespace if it fits).
for example, constructors and destructors can be abbreviated to just Class::Class and Class::~Class
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
Start at the HTML report's C++ demangling path and inspect how long symbols are currently rendered. Done means very long names prioritize the class and function, retain a namespace when it fits, and abbreviate constructors or destructors as Class::Class or Class::~Class.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100