Where are we going? CLion 2018.2 roadmap
Just recently we’ve released CLion 2018.1! It improved C++ support with dozens of fixes and several important C++17 features supported, provided the ability to compile, run, debug and run with Valgrind Memcheck Linux binaries on Windows using the WSL toolchain, added CMake Install and started the general decoupling of the CMake project model from CLion, enlarged the supported family of languages with Rust and Fortran, and much more.
Now it’s time to thank our evaluators for their great help and share plans for 2018.2 coming in mid 2018.
It always happened to be quite hard to check new changes in all possible environments and configurations, so evaluator’s help is always highly appreciated, as they help us to make the release stable and feature-rich. We have an ongoing tradition to thank our most active EAP evaluators here in the blog and present each of them with a free 1-year subscription for CLion (to extend their current subscription or get a new one). This time we’d like to issue a special thank to the following contributors:
- Taw Moto (YouTrack handle: tau.xxx)
- Oliver Stöneberg (YouTrack handle: Firewave)
- Sascha Kratky (YouTrack handle: sakra)
You will receive a personal email with details on how to claim your license. (If, for some reason, you do not get an email from us within a week, ping us here in the comments!)
CLion 2018.2 plans
We’ve already outlined the major directions and priorities for this year: improve C++ support (both in terms of correctness and IDE performance), focus on remote development and enrich the project models support. These goals remain, and the plans for 2018.2 are all created with these directions in mind.
- C++ Support
While considering different alternatives to the current language engine, doing various tests and measurements, we still work hard on the current implementation, fixing bugs and adding support for the new language features:
- More C++17 features
- Fixing issues with incorrect code parsing, resolve and false code analysis warnings across different code bases and code samples
- IDE performance
We’ve collected and sorted dozens of various freeze dumps and snapshots, and started working on globally improving the situation in 2018.1. Better typing performance was just the first step. We’ll continue to fix cases with freezes on typing, completion and some other popular IDE actions.
- Compiling / Running / Testing
- Add an option to (re)compile single files
- Add Google Sanitizers support
- Project Model
- Continue with decoupling CMake from CLion, work on project model API
- Investigate alternative project models
- Improve experimental hex support in debugger
- Add memory views
- Add LLDB disassembler support
- Remote development
- Implement first prototype for remote development support, limit target system to Linux, other limitations are possible
- WSL support improvements
As usual, your feature requests and suggestions are welcome in our tracker.
Your CLion Team
The Drive to Develop