CLion 2018.2 Release Candidate 3

Hi,

A new CLion 2018.2 Release Candidate is now available (build 182.3684.76)!

Please note that to use CLion 2018.2 RC3 you need to have an active subscription (or start a 30-day evaluation period).

Download CLion 2018.2 RC3

Our Early Access Program lets development community closely participate in discussions devoted to our products and identify issues that were possibly overlooked by our team. Unfortunately, one of such issues – CPP-13704 – is related to the new experimental clangd-based language engine on Windows. Since we can’t provide a reliable solution quickly, we decided to turn clangd-based language engine off by default on Windows. You still can enable it in Settings/Preferences | Languages & Frameworks | C/C++ | Clangd, but in this case mind the bug.

This has an unfortunate consequence – argument selection defects inspection was implemented on top of clangd-based language engine (this solves a performance issue and some others). That means that on Windows the inspection is not available unless you turn on the clangd in CLion’s settings.

Full release notes are here.

Your CLion Team
The Drive to Develop

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

8 Responses to CLion 2018.2 Release Candidate 3

  1. Roman says:

    Does Linux version has the same clangd issue? Do you have a plan to how to fix it on Windows?

    • Anastasia Kazakova says:

      No, clangd works with memory in a different way on Linux/macOS, so these platforms are not affected. Windows – we are currently working on the fix, but it’s definitely non-trivial and non-obvious, so for now we turned off by default (but you can enable anytime).

  2. Haha says:

    When remote develop by ssh is OK?

    • Anastasia Kazakova says:

      It’s currently under development. We can’t estimate right now but how to get some things done for 2018.3

  3. Victor Sergienko says:

    May I attract some love for CPP-11047?
    A (hopefully) trivial one that’s so much needed from time to time.
    Thanks!

  4. haha says:

    Can’t recognize redefined macros.

    #define assert(expr) foo(expr)

    #undef assert

    #assert(expr) check(expr)

    asssert(1111); //ctrl+click, jump to “#define assert(expr) foo(expr)”

Leave a Reply

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