CLion 2018.2.1 update enables clangd on Windows


CLion 2018.2 release has happened just recently. And today we are happy to announce that the first bug-fix update 2018.2.1 is now available. If you haven’t yet upgraded to CLion 2018.2, good time to do so right now!

Get a fresh build from our website, use Toolbox app or snap packages (in the case of Ubuntu) to update. A patch-update will be available shortly for those using CLion 2018.2.

Download CLion

Clangd-based language engine on Windows

In this build the experimental clangd-based language engine is finally enabled by default on Windows (previously we enabled it by default on Linux and macOS)! It’s still used only to show errors and warnings in the editor, however that means that you get more accurate error highlighting on all platforms by default.

If you experience any issue with it, report it to our tracker, customize the settings or turn the engine off in Settings/Preferences | Languages & Frameworks | C/C++ | Clangd.

And more

Other fixes include:

  • A fix for a UI freeze when sanitizers are used (CPP-13341).
  • Fixed poor performance of VCS repository detection (related to symlinks).

Full release notes are available by the link.

If you are interested in what’s coming in CLion 2018.3, check the preliminary roadmap here.

Your CLion Team
The Drive to Develop

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

6 Responses to CLion 2018.2.1 update enables clangd on Windows

  1. Pete says:

    I am happy that Clangd works now for windows. False error detection due to CPP-3560 had colored big parts of my source code red …

  2. Pete says:

    The syntax check is much better. But unfortunately after the position the original CLion scanner falsely detected the error, the lookup and color coding is not working for enums. I must add, that all this is inside a 600 lines predefined integer array with thousands of constants.

  3. Pete says:

    I will try to make a small sample this weekend and put it in the tracker

Leave a Reply

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