You need to have the tool installed to get proper Rust support. Your system needs to recognize *.rs files as text/ rust mime type, otherwise Develop won't activate this plugin for them.
You should see this file installed to your system (the exact path may vary): In Develop navigate to Settings Configure Develop Plugins and enable Rust Support plugin.
If you installed the rustc2duchain tool into your rust up's nightly bin directory the plugin should work out of the box. Set path to directory with rust libraries.
Errors and warnings should be visible in Problems tool view. I'd like to highly encourage everyone to give it a look now that it's finally considered ready for prime time.
To aid the effort I've put some Sunday hacking time into a basic Rust code completion plugin for Kate today. Completion' The plugin is very basic at the time of writing (which is minutes after getting things working, this Sunday is running out!).
Ditto for auto-completion behavior (i.e. defining the circumstances in which the completion popup will kick in automatically, as opposed to waiting for manual invocation) and simply performance. The Rust community in particular maintains an official Kate syntax highlighting file here.
The repository for the Kate plugin includes this as a submodule and installs it by default; if you'd like it not to do that, there's a build system toggle to disable it. It turns out there isn't a MIME type for Rust source code in shared-mime-info yet, so I've started the process of getting one in.
This location might change if/when the plugin is promoted to proper project status; I'll update the post should that happen. You can get it by building Kate from git as whole, or you can do make install in just the plugin's submit of your build Dir; at this time it works fine with Kate's last stable release.
Given all this, I'll only quickly recap some additional info for getting it working here: Once you've enabled the Rust code completion item in the plugin page, a new page will appear in your Kate config dialog. If you have any comments or requests and the blog won't do (say, you have a cool patch for me), you can find my mail address inside the AUTHORS file included in the repository.
After more than a year of continuous work by our community, I'm very pleased to finally announce the first beta release of Develop 5.0.0. We replaced our legacy C++ parser and semantic analysis plugin with a much more powerful one that is based on Clang from the LLVM project.
Finally, we cleaned up many areas of our code base and improved the performance of some work flows significantly. We spent a lot of effort on keeping the porting bugs to a minimum, and our thanks go out to the many testers who have guided us in the process.
Adding support for all the quirky corner cases in C++, as well as maintaining compatibility with the latest C++ language standards such as C++11, drained our energy and stole time needed to improve other areas of our IDE. Furthermore, the code was so brittle, that it was close to impossible to improve its performance or add bigger new features such as proper C language support.
Now, after close to two years of work, we finally have a solution to this dilemma: A Clang based language plugin. But the new Clang based plugin finally scales properly with the number of cores on your CPU, which can lead to significantly improved performance on more modern machines.
Instead, we now use metadata provided by Make itself, giving us a correct listing of targets, as well as all include paths and defines for the source code files in your projects. But this step also means that we had to remove some useful advanced Make integration features, such as the wizards to add files to a target.
We are aware of this situation, and plan to work together with upstream to bring back the removed functionality in the future. Hopefully, you agree that correctness and much improved performance, where opening even large Make projects is now close to instant, makes up for the loss of functionality.
To conclude this long announcement, I want to express my sincere gratitude towards the dozens of contributors that have worked on Develop 5 over the last months. Built on modern open source technology, the Develop IDE offers a seamless development environment to programmers that work on projects of any size.
At the core of Develop lies the combination of an advanced editor with semantic code analysis, which delivers an enriched programming experience thanks to a deep understanding of your project. Supported platforms include Linux, Polaris, FreeBSD, macOS and other Unix flavors as well as Microsoft Windows.
We will be going through all the important graphic settings, how to change your resolution (NVIDIA & AMD users). These settings are optimal for PVP, but can also be used for players struggling to reach their monitors refresh rate...
You will no longer see objects breaking (No FPS drops while raid towers are demolished) Long distance fights you'll be able to see through certain trees and bushes (200-300 m) Sound will be improved if you've forgotten to use the optimal settings. You will reach 150+ FPS with a decent PC, if you have a high-end PC then you might consider lowering your resolution to be able to reach a stable FPS above your display's refresh rate.
If you play other competitive games on a lower resolution you might consider lowering it, some of the best players in Rust play on lower resolution in order to maximize FPS, however it's not worth it if you're playing on a 60Hz screen (unless you have problems reaching 60FPS)You can change your resolution when you start rust, however if you want to remove black bars then do this. My single most favorite feature is “go to symbol” (Ctrl+Alt+Shift+N), which allows you to quickly navigate to any item in the local crate or in a dependency (standard library is not yet supported because it’s a bit of a hassle to download its source code).
We also have “go to definition” for local crate (Ctrl+B), file overview (Ctrl+F12) and a simple completion. For example, a quick fix to create a module file if you have mod foo;, but no foo.rs, or context sensitive snippets (f and pf expand to field definition if you are inside a struct).
On the technical side of things, the plugin is implemented in Kotlin, which is a real breath of fresh air in the Java world. We do not use Racer, and we likely won’t be a heavy user of the upcoming RLS.
Following the good old IDEA tradition, we have implemented our own parser and symbol resolver. It’s a ton of work, but it allows us to readily reuse IDEA’s powerful indexing frameworks.
Please may I ask you to describe how to set up the IDE after installing the plugin successfully. For example, where to set up the rust source directory and other important setting for best user experience.
But I haven’t tried it on Windows myself, so I guess there might be some hiccups, especially with importing projects. How to set up the compilation from the IDE(I still haven’t figured how to make this work properly, what I currently do is “Edit configurations” set an external application that runs “cargo build” from ProjectFileDir then I press to compile, let it complain that I didn’t set a module(which cannot be set) and press “Continue anyway” after which I just rerun with “Ctrl + F5” or the button).
We’ve merged this functionality only tonight, so it’s not surprising your we are unable to figure it out =) That is, it won’t work for struct fields and “member functions”.
Go to symbols is for navigating to items (functions, structs, traits, modules). No, we are using cargo metadata command to learn about project structure and dependencies.
Matilda I feel bad for jumping with the issues before thanking you guys for the great work you did and do. I think this is the only proper IDE integration with that extensive test suite you guys developed.
I sincerely appreciate that you guys do this work, this helps the entire community in a very considerable way. Matklad: Following the good old IDEA tradition, we have implemented our own parser and symbol resolver.
First thing that came to my mind when I saw this message is Qt Creator and Develop in the C++ world. Both of these IDEs had their own parsers and now they came to a moment where they just can’t compete and keep up with the changes in the language and the information that a compiler can offer.
Please note that you’ll have to update your Kotlin plugin for this to work. Update: Yep, I installed IntelliJ 16 Preview and it now works beautifully.