CLion 2018.1 Release Candidate

Posted on by Anastasia Kazakova

Today we are glad to announce CLion 2018.1 Release Candidate (build 181.4203.106). We encourage you to try the build and kindly ask you to share your feedback and comments with us and report any bug at all to our tracker.

Download CLion 2018.1 RC

No active subscription is required.

This build brings:

  • Fixes for multiple code analysis false positives with Clang 5 (CPP-10694, CPP-10947).
  • Fixes for anonymous bit fields parsing (CPP-6665).
  • Anonymous structures (Microsoft extension) are now supported in parser.
  • Small usability improvements of Import Project functionality (CPP-11840).

Meanwhile, if you are developing in Fortran or Rust, check the corresponding plugins available for CLion 2018.1 EAP. Debugger is available for both languages, and in Rust benefit from Cargo support (instead of using CMake).

Full release notes are available by the link.

Your CLion Team
JetBrains
The Drive to Develop

Comments below can no longer be edited.

14 Responses to CLion 2018.1 Release Candidate

  1. Pavel says:

    March 15, 2018

    Hello, Anastasia

    Could you pay attention to bug with Pimpl? It’s really annoying when IDE can’t resolve pointer to forward declared struct.

    Cheers

    • Anastasia Kazakova says:

      March 15, 2018

      Could you please point to the issue? Can’t find it from the first look through

      • Pavel says:

        March 15, 2018

        I’ve found an example of my problem: https://youtrack.jetbrains.com/issue/CPP-9949#comment=27-2408307

        IDE can’t resolve a type of pointer to an implementation (in the example it’s the variable impl), and as the result code highlights in red.

        I noticed this problem few EAP versions ago.

  2. Yaroslav says:

    March 16, 2018

    Since the last EAP (and also this RC) JS support is too buggy in CLion.
    Tones of exception during debugging sessions (JSDebug).
    I am not sure how WEB plugin is synchronized with CLion but current state definitely is not production ready.

  3. Arthur J. says:

    March 18, 2018

    Hello, if I’m on stable 2017.4, should I update on this RC (i.e. is it enough stable?) to start using new features (WSL related ones) or should I wait for the stable release (what’s the release window in this last case) ?

    • Anastasia Kazakova says:

      March 19, 2018

      Release Candidate is a pre-release build, so is more or less stable, though some issues are still possible. The release will be published in a couple of weeks. Stay tuned.

  4. Victor Sergienko says:

    March 19, 2018

    Thanks for the release!

    Now, whining.
    The out-of-the-blue 100% CPU usage is a bummer. I’m lucky I have 700% more.
    I did create an issue and uploaded several CPU dumps there: CPP-12217.
    And my favorite stress test, Battle for Wesnoth sources, still gives a ton of false positives: CPP-11097

    • Anastasia Kazakova says:

      March 20, 2018

      We have a huge overhaul there, moving forward for a couple of releases. Hope to improve the IDE performance soon.

      • Kirill Sapozhnikov says:

        March 22, 2018

        I hope improving performance will make working with libraries like boost comfortable. Now it’s painful due to long code resolving.

        • Anastasia Kazakova says:

          March 22, 2018

          Boost is a hard library for IDEs indeed. Do you experience problems when typing or calling some specific actions?

          • Kirill Sapozhnikov says:

            March 23, 2018

            Well, it feels like there are problems with everything. Syntax highlighting (long), symbols resolving(even longer), auto completion (incredibly long or even doesn’t work).
            It all gets worse the more files in project use Boost. BTW, same with Eigen.

          • Kirill Sapozhnikov says:

            March 26, 2018

            QtCreator works fine with Boost.

          • Kirill Sapozhnikov says:

            March 26, 2018

            And MS Code

Subscribe

Subscribe for updates