CLion 2017.3 EAP: bug-fixes in C++ support

Hi,

A new CLion 2017.3 EAP (build 173.2463.5) is now available and addresses the following issues:

  • Issues in CLion’s language engine related to array usages are fixed. This covers mostly incorrect overload resolution behavior, which leads to false-positive warnings (CPP-7860, CPP-9491 and CPP-10231)
  • For -include option, support for values provided without a space after the option’s name is added (CPP-10351).
  • In case you are using C+17, for C++17 features that are not yet supported in CLion, a workaround is added to avoid (where possible) bogus warnings and errors in the code highlighter.

The full release notes are available here.

Download CLion 2017.3 EAP

Your CLion Team
The Drive to Develop

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

11 Responses to CLion 2017.3 EAP: bug-fixes in C++ support

  1. Olof says:

    From the release notes it appears that this still is an issue:

    https://youtrack.jetbrains.com/issue/IDEA-178869
    IDEA-178869 JNA is broken on CentOS 6

    Any news about whether there is a workaround or if it might have made it into this release or neutralized in some way?

  2. Cedric says:

    Love to hear that array issues have been fixed! Also didn’t know theres a release notes page! Can’t wait for more features / fixes 😉

  3. Roman says:

    Looks like bundled CMake is broken:
    CMake Error at
    clion-173.2463.5/bin/cmake/share/cmake-3.8/Modules/Compiler/VisualAge-CXX-DetermineCompiler.cmake:4
    include could not find load file:
    clion-173.2463.5/bin/cmake/share/cmake-3.8/Modules/Compiler/IBMCPP-CXX-DetermineVersionInternal.cmake

    I’ve opened a directory, and file is named IBMCPP-CXX-DetermineVersionInternal.cmak , without ‘e’ at the end.

  4. Crull says:

    “In case you are using C+17, for C++17 features that are not yet supported in CLion, a workaround is added to avoid (where possible) bogus warnings and errors in the code highlighter”

    This is excellent! Thank you! Keep on the good work in eliminating all false positives!

    • Anastasia Kazakova says:

      That’s just a workaround for now until we properly support C++17. Thanks.

      • Crull says:

        I fully understand that and I very much appreciate it. Bogus warnings and errors could be very distracting! Thank you very much for taking care of them until you implement proper language support!
        This is also a good step as there will be much more C++2x syntax in the future too and the compilers are already implementing the newest features.

  5. mbalabin says:

    Hi! Is there any chance that https://youtrack.jetbrains.com/issue/CPP-7166 will get a priority boost? The issue has been hanging in the tracker for a year and it was already been duplicated more than ten times. I remember you wrote that it will require some extensive refactoring in variable caching infrastructure to fix. But the sheer number of duplicates shows that it is affecting a lot of users in their everyday work. I humbly ask you to give it a push on the next planning session.

    Btw, the page https://www.jetbrains.com/clion/nextversion/ contains a wrong link to the blog post for this EAP.

    • Anastasia Kazakova says:

      Thank you for your comment.

      CPP-7166 is on our roadmap, but we have really a lot of things in debugger with high prio, so it was delayed for a while. Hope to get to it soon. Thanks for reminding.

      > contains a wrong link to the blog post for this EAP.
      Thanks, indeed, we’ll update.

Leave a Reply

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