Hi,
The new CLion 2018.1.2 Early Access Preview build (181.4668.25) is now available! Download it from our site or, in case you are using CLion 2018.1.1, install via a patch-update that will become available shortly.
Please, note that this EAP build requires an active subscription (or you can start a 30-day evaluation period).
This EAP build addresses the following issues:
- Incorrect ‘Class is never used’ inspection (CPP-5345). CLion now handles cases with constructor correctly, for example:
- Completion for template classes was showing duplicated names in case of specialized declarations (CPP-12351)
It also improves the IDE performance on projects with many friend operators (like Eigen) – CPP-12321, and removes some infinite recursion in code resolve – CPP-12290.
Besides, this build brings fixes for a couple of annoying regressions:
- Incorrect code analysis for pointer to implementation pattern (CPP-12526)
- Incorrect warning about std::cin argument (CPP-12515)
- Incorrect parsing of the type cast used in constructor calls (CPP-12428)
- Completion didn’t work for enum variables in if statements (CPP-12287)
Full release notes are available here.
Your CLion Team
JetBrains
The Drive to Develop
Excited about the fixes to pimpl parsing !
struct A {
A(const B&) { }
};
struct B {
B(const C&) { }
};
struct C {
C() { }
};
int main() {
A a(C()); //cannot resolve converting constructor
}
Seems the sample is missing some forward declarations, isn’t it?
Sorry, look at the following complete examples:
struct B;
struct C;
struct A {
A(const B &) {}
};
struct B {
B(const C &) {}
};
struct C {
C() {}
};
int main() {
C c;
A a(c); //cannot resolve converting constructor
return 0;
}
Thanks, reproducible on our side. We’ll check if that’s smth new (regression) or some known issue. And will be back to you
Seems like a regression: https://youtrack.jetbrains.com/issue/CPP-12744
Thank you!
I see this EAP solves many code resolving/parsing bugs. Will there be a release for 2018.1 that is targeted for solving performance problems or we have to wait for 2018.2?
There are some tickets in progress. We’ll see if it is possible to back-port to 2018.1. If there are many code areas affected, they might be not.
I also agree that the performance problems should be the top priority of CLion. It is a mature and a great IDE but it’s the slowest IDE on the market. In 2018.1.1 there are a lot of new bugs regarding performance, besides the one already opened.
I also get a lot of slow-typing sometimes, which I already mentioned almost 2 years ago, which are not yet fixed. Now I see that other people complained about this.
Sorry to tell you this, I really really love CLion but I got more lags(slow typing) with CLion in the last 2 years that I got with the other IDEs in my 13 years’ programming career. And I don’t work with such a big project, it compiles in 5-6 minutes.
I understand this looks disappointing to you. I can only tell you here that 1) unfortunately sometime performance issues appear after correctness fixing 2) we are on it (performance and freezes) and have some plan how to overcome current problems. We have the work in progress, so you can expect improvements.
Thank you for the answer, I will wait for the performance increase.
Btw, nice great talk at ACCU :).
Thank you!
Hello, I have a problem with this EAP build.
Code inspector says the following code is wrong with message “Types ‘const std::function’ and ‘void (*)()’ are not compatible”:
const std::function f = []() {};
But it was OK with previous CLion versions.
It seems like this one https://youtrack.jetbrains.com/issue/CPP-12535
Should be fixed in some upcoming 2018.1.x update
Please speed up the performance issues. I’ve been using it for a year now with somehow tolerable waiting (sometimes a few minutes for a project to open), but the 2018.1.1 became useless for me. Current project takes 3h to open. I didn’t try to open the previous projects to know whether its only this one or general, because I don’t want to lose even more time.
It’s the best IDE otherwise, but unfortunately not usable since its so slow for me (2018.1.1). It’s refreshing files and blocking work, even if no changes in any of the files, except a new line or a typo in CMake.txt. One thing that I suspect is an include that has 4k header files, but I cannot avoid it, except manually chase the headers and copy them on another place.
To make my statements less harsh, it does start fast enough if I don’t include that folder. Still, if possible please make ‘refreshing files’ and other parts non blocking. Also I didn’t find a way anywhere to enable logging, so I would be able to see which operation gets the operation stuck.
3h – is it for the initial indexing? How the IDE behaves after the project opening? Do you experience UI freezes?
What the size of the project? What C++ standards / features is it using? Are there many huge files, headers?