CLion 2016.3 EAP: fixes in code analysis
Hi,
Fresh CLion 2016.3 EAP build (163.6110.22) is out! It addresses a couple of important issues and in general makes CLion 2016.3 more stable.
Code analysis
We continue our work on making CLion’s code analysis more accurate by reducing a number of false-positives. CLion now considers non-trivial destructors in the ‘Unused variable’ inspection. This brings a fix for incorrect ‘Unused variable’ for the so called ‘guard’ idiom, that is used to make code exception-safe and to save/restore the context before doing some job. The typical example is std::lock_guard:
CLion showed the “Local variable is only assigned but never accessed.” warning previously – now the problem is eliminated.
Besides, this brought a support for __attribute__(unused). When it’s used, CLion doesn’t warn about an unused variable any more:
Another false inspection fixed is reporting possibly a null reference where it’s not the case (CPP-3043).
Other fixes
- Thanks to our user, who reported a problem with Doxygen comment generation, an issue for generation in directive block was found and fixed.
- There was quite an unpleasant hang when IDE was updating indices and a modal window was opened (CPP-7818). The problem is eliminated in this build.
And, by the way, looks like the Lua plugin was recently updated and now can be used inside CLion. There are still some known issues but the basic functionality including run configuration creation, completion, navigation, find usages and more works.
As usual, full release notes are available by the link.
Download the build or get a patch update in case you are using previous CLion EAP, build 163.5644.7.
Your CLion Team
JetBrains
The Drive to Develop
Subscribe to CLion Blog updates
