CLion 2017.2 EAP: code analysis fixes

Posted on by Anastasia Kazakova

Hi everyone,

We are glad to announce that new CLion 2017.2 Early Access Preview build (172.2465.12) is now available. Download it from our site or get a patch-update if you are using previous EAP build.

This build addresses the following issues:

  • Incorrect code analysis when std::enable_if is used (CPP-3632, CPP-9281).
  • For GCC5/6 CLion failed to resolve STL containers with nested template type correctly in case “using namespace std” was used. That caused incorrect no matching function and other errors when accessing container’s member.(CPP-8638, CPP-9412, etc.). Please.
    note, for MinGW-W64 & GCC 6.3 the problem is still there (CPP-9796).
  • Incorrect “Declaration of const variable requires an initializer” in case of a static const field (CPP-1145) or constexpr (CPP-9340).
  • Out of memory issue (regression) when the code uses boost::property_tree.
  • Git Revert command is now available in the Git Log view. Select any number of commits and call Revert from the context menu.
    revert_git

And there is more! Check the full list by the link.


Download CLion 2017.2 EAP

Your CLion Team
The Drive to Develop

Comments below can no longer be edited.

2 Responses to CLion 2017.2 EAP: code analysis fixes

  1. RAN says:

    June 13, 2017

    I use Clion with Cygwin, want C++17,
    So I use gcc source code build updated gcc from 5.4.0 to latest 7.1.0.
    it’s path at /usr/local/bin/gcc-7.1.0.exe, not the default gcc compiler.
    when use CLion(2017.2 EAP) create project(C++ Executable), it only can select C++11 and C++14, not see C++17.
    Through modified CMakeLists.txt to set(CMAKE_CXX_STANDARD 17), compile errors.
    Is there anything wrong?
    How to change CLion gcc compiler enviroment?
    CLion auto detected at D:\Cygwin64\bin\C++.exe

Subscribe

Subscribe for updates