CLion 2017.1 EAP: more C++14 support


Last week CLion 2017.1 Early Access Program started with a new make auto intention, auto return type support, zero latency typing mode and many important improvements. This week a new EAP build (171.2822.8) is available. In case you use the previous EAP build, you should get a notification in the IDE about a patch update shortly.

Download CLion 2017.1 EAP

Generic lambdas

Modern C++ standards support is one of our top-priority task for this year. We keep working on C++14, and while first EAP brought auto return type support, this build comes with the generic lambdas support. This includes correct type inference and corresponding code analysis checks:

More C++14 features are coming to CLion in the next EAP builds. You can check what’s left in our webhelp.

Decltype cases

This EAP also addresses several cases with decltype when the code was not resolved correctly:

  • decltype(auto) used in trailing return (CPP-6075)
  • Constructors using decltype (CPP-8195)

Other fixes

Besides, this build includes a couple of other fixes for incorrect code analysis or refactoring:

  • Fix for the incorrect Explicit type required here warning when declaring a friend class (CPP-2637)
  • The refactoring of the ambiguous calls is disabled to avoid problems (CLion shows Function foo is ambiguously referenced warning in this case)

That’s about it. The full release notes are available here.

Download CLion 2017.1 EAP

The CLion Team
The Drive to Develop

This entry was posted in Announcement, Early Access Preview and tagged , , . Bookmark the permalink.

17 Responses to CLion 2017.1 EAP: more C++14 support

  1. lenfien says:

    Hi, dear developers, please , support remote toolchains like netbeans. Please….

  2. Olof says:

    It seems as if an instability has been introduced in this version of the EAP, and persisting into the next version.

    What happens is that when I open a particular header file, not very big, maybe 300 lines long the IDE freezes. It doesn’t immediately freeze which makes me think that it is some sort of background processing that makes that happen.

    Unfortunately I can’t share the file. This has happened to both me and colleagues for the same file.

    I upgraded to the newer EAP in the hopes that the instability would disappear. I have not downgraded to make sure that this was introduced in this EAP.

    I’m sorry for the poor information but it is all I have at the moment and I have to move onto working on other things.

    • Anastasia Kazakova says:

      If there was a freeze, there should be a thread dump generated? Could you please check in the same directory where the IDE logs are?

      • Olof says:

        Where should those be uploaded to?

        They need to be uploaded to a private place. The company I’m working for is very persnickety about leaking any information so our IT department is also working with setting up an NDA with Jetbrains. So it is important that it gets sent to a private place.

        If we can get this process working I’d be happy to send those reports in the future as well to help CLion stabilize.

        • Anastasia Kazakova says:

          Submit a request via our support:
          However, thread dumps are safe as it’s the state of the CLion itself, so it doesn’t contain any links to your code.

          • Olof says:

            Unfortunately where I work is very strict with things like this, even if it feels like a thread dump is safe.

            Anyway, there is a new behavior that I’m observing.

            I’m not sure when it started, but it was in one of the EAP’s. I’m currently running the latest EAP, 3566.

            Now when I start the project it appears to start up very fast, but then the IDE locks for about a minute before it responds to clicks and there is no little progress bar at the bottom to show that it is working on something. I looked and that does produce a threadDump. I thought I’d share what little I do know about this behavior.

          • Anastasia Kazakova says:

            That’s interesting, but we can’t reproduce it unfortunately. Could you make a thread dump on your own as described here: Or a CPU snapshot for the moment the problem happens.

          • Olof says:

            The NDA situation has been sorted out, so our IT department should be sending a bunch of threadDumps to you shortly.

            The startup issue threadDumps should be in there I hope.

          • Anastasia Kazakova says:

            Great. Are you submitting through the support? How can I identify you there? Could you please provide a link to this thread may be while submitting?

          • Olof says:

            Can you see my Email that I typed in for this post? It’ll be submitted by another guy from the same company.

  3. Olof says:

    Should be submitted now. I was able to do it so I linked this thread.

  4. stanley says:

    nice blog post thank you for the write up.

Leave a Reply to Anastasia Kazakova Cancel reply

Your email address will not be published. Required fields are marked *