CLion feedback
Hello,
being a long time CLion user (however not exclusively, for reasons described below), and having kept silent for several months, I want to give some feedback again.
1. I have given up on CLion debugger. After several years, the situation has not improved much. The value inspectors still don't work, and every now and then, the debugger doesn't even start and reports something about a bad "A" packet. QtCreator's debugger is still the only safe choice (don't bother asking for details. As I said, I've given up)
2. The parser seems to be deteriorating as well, recently. I have large stretches of code that are marked red by the parser, but compile perfectly well. This did not happen with older versions of CLion
3. As happens often with JetBrains, rather than fix fundamental malfunctions, they introduce GUI gimmicks. Lately, a change was introduced that makes menus not drop down from the top as usual, but "explode" from the middle. Very annoying. I like my UI with as little gimmickery as possible. Didn't find a switch to turn this off
Bottom line: Clion is still the most convenient C++ code editor, but by a shrinking margin
regards,
Christian
请先登录再写评论。
Hi!
We are sorry for the inconvenience.
>The parser seems to be deteriorating as well, recently.
We are trying to fix regressions as fast as possible. We've fixed some in updates to CLion 2018.1 (in 2018.1.1 and 2018.1.2). The details can be found in our blog.
>Lately, a change was introduced that makes menus not drop down from the top as usual, but "explode" from the middle.
If I understand the issue correctly, that's a platform bug: https://youtrack.jetbrains.com/issue/JRE-710. The possible workaround is described in this comment, please try it.
Since the appearance of C++20 CLion must contain a new debugger capable of deconstructing the Metaprogramming. Already now my constexpr make up 60% of the program due to massive overloading. But there is now no way to check on typenames if they behave correctly while compiling.