devblogs.microsoft.com
Developer Activities Survey Results Overview - C++ Team ...
Excerpt
| |**Top 7 Tasks Cited As Pain Points By Aggregate Score **|** (Normalized Score Ranking) **| |--|--|--| |1|Refactor – Rename Item (var, meth, etc.)|2| |2|Refactor – Extract Method (copy/paste)|3| |3|Jump between header and source|4| |4|Refactor – Code Cleanup (copy/paste)|5| |5|Understand compiler outputs (errors/warnings/etc.)|6| |6|Open file/Load project – time to edit|10| |7|Align code to coding style|7| It’s no surprise that every refactoring topic offered in the survey made it to the top of the pain points list. It is well-known that the lack of support for C++ refactoring is widely felt. **AH, BUT WHAT’S THIS?!** Many of you are probably wondering which task made it to the top of the normalized list, and you should! Take a look for yourself: … - *STL errors are seriously convoluted. I had one last week where a modification on line 500 caused an “error” on line 100. And the error was in a different function! * - *My solution takes a long time to load. It can be slow editing large projects. [VS2012] *
Related Pain Points
Code refactoring support in C++
6Refactoring operations (rename, extract method, code cleanup) are the top pain points in C++ IDEs, indicating widespread lack of automated refactoring tooling.
Poor compiler error messages for templates
6C++ compiler messages are unhelpful when template code is incorrect, making debugging difficult. C++20 concepts help but require significant effort to understand.
Slow project loading and navigation in large codebases
5Opening files and loading large C++ projects is slow, and navigation between header and source files is cumbersome, causing delays during development.
Enforcing code style and alignment
4Aligning code to project coding standards and automatically enforcing style conventions is a pain point in C++ development workflows.