by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 21:21
    github-actions[bot] milestoned #6152
  • 21:20
    bors[bot] closed #6152
  • 21:20
    bors[bot] closed #6150
  • 20:42
    Undin ready_for_review #6152
  • 19:35
    Undin synchronize #6152
  • 17:37
    dima74 assigned #6157
  • 17:37
    dima74 opened #6157
  • 12:33
    vlad20012 edited #6156
  • 11:11
    vlad20012 synchronize #6156
  • 11:10
    vlad20012 edited #6156
  • 11:08
    vlad20012 labeled #6156
  • 11:08
    vlad20012 assigned #6156
  • 11:08
    vlad20012 opened #6156
  • 08:05
    github-actions[bot] milestoned #6155
  • 08:05
    bors[bot] closed #6155
  • 07:27
    Undin opened #6155
  • 07:23
    Undin synchronize #6152
  • 05:07
    akainth015 synchronize #5014
  • 04:18
    akainth015 synchronize #5014
  • Sep 23 22:45
    akainth015 synchronize #5014
Andrey Cherkashin
@andoriyu
Is there an easy way to move certain methods and structs into separate module?
Arseniy Pendryak
@Undin
@umanwizard hi! Is new macro expansion engine enabled? See intellij-rust/intellij-rust#3628. Looks like it should solve your issue. Note, it's not about cargo features, it's about modules declared inside macro calls
Arseniy Pendryak
@Undin

Is there an easy way to move certain methods and structs into separate module?

@andoriyu Unfortunately, it's not supported yet. We've just started working on move refactoring (see #5181)
Could you please file an issue with the desired feature?

Vladislav Golub
@vagola
Hello! After upgrading to latest idea and rust plugin i have lost colors. Like code not recognized
Vladislav Golub
@vagola
@Undin ty
Samuel Rufinatscha
@rufsam
Hey guys! When I use something like let (shutdown_sender, shutdown_receiver) = oneshot::channel(); spawn(async move { shutdown_sender.send(()).unwrap(); }); it compiles fine and i can execute it, but the plugin shows up Cannot borrow immutable local variable shutdown_sender as mutable? Do you have an idea what I'm doing wrong here?
Nils Olsson
@nilsso
is there's a nice way to invoke wasm-pack build as a configuration in CLion
Ara
@Minosian_gitlab
  • Open project
  • Add configuration
  • Templates/Cargo command
  • Specify working directory: root directory of project with workspace
Configuration produce an error in "Edit configuration" window - "Error. No Rust toolchain specified"
Ara
@Minosian_gitlab
Eventually I found a solution by myself. I clicked "cargo" ticket on right window side and chose "Run Cargo Command". After this "run configuration" works normally.
Psilon
@Pzixel
Hey, I have a problem for some reason this code gets compiled but it doesn't pass plugin typecheck
image.png
I've enabled experimental engine
@vlad20012
could you elaborate, please?
Hari Bhaskaran
@yetanotherfella_twitter
I have followed the suggestions in https://github.com/intellij-rust/intellij-rust/issues/5225#issuecomment-612191194 , but I still can't navigate into any definition inside an external crate
Vesa Vilhonen
@vvilhonen
hey, and thanks for the amazing plugin!
I have some problems with tokio_tungstenite, which is re-exporting tungstenite like this https://github.com/snapview/tokio-tungstenite/blob/master/src/lib.rs#L19
intellij-rust can't see any of the re-exported symbols even after invalidating caches
Vesa Vilhonen
@vvilhonen
I'm running idea 2020.1.1, intellij-rust 0.2.122.3105-201 and rust 1.43.1
I don't remember encountering problems with autocompleting re-exports last year but now it happens with every crate using them
using experimental macro engine
is it supposed to work and how should I start debugging to find the root cause?
Vesa Vilhonen
@vvilhonen
I seem to be experiencing this intellij-rust/intellij-rust#4209
if I change pub use tungstenite to pub extern tungstenite in tokio-tungstenite, the autocompletion works
Vlad Beskrovnyy
@vlad20012
image.png
Teiva Harsanyi
@teivah
Hello guys! I'd like to know if there's a way to trigger cargo check once the file is saved (not on the fly which seems to be really heavy). And I would like this to be integrated with IntelliJ (I mean as far as I saw, if I configure a file watcher, I'll get the problems in the terminal, not on the editor itself)
Teiva Harsanyi
@teivah
it's super slooooooooow
am I the only one struggling with IntelliJ & Rust?
Jakub Beránek
@Kobzol
what exactly do you experience as slow? in my experience the biggest boost for IntelliJ's performance is SSD :D
Teiva Harsanyi
@teivah
cargo check!!
I mean I did not find how to setup cargo check only once I save the file!
I mean not from a file watcher, I want the compilation errors to be seen on the editor directly (not the terminal)
Jakub Beránek
@Kobzol
If you open the Cargo window and use the "Run external linter" action, it will run the linter in the IDE and display errors in a structured way, with direct links to source code etc.
I usually bind the action to a keybind and run it after I change something and I want to lint it.
Settings -> Keymap -> Run External Linter
Teiva Harsanyi
@teivah
mmh I see, yes thanks that's not too bad I suppose
Jakub Beránek
@Kobzol
You can also choose whether to run cargo check or cargo clippy in Settings - > Languages & Frameworks -> Rust -> Cargo -> External linter
Teiva Harsanyi
@teivah
I would have preferred if we would had a Run external linter on save in Languages & Frameworks -> Rust -> Cargo
but at least thanks, it's kinda saving my day ;)
Jakub Beránek
@Kobzol
I'll create an issue for that and if it seems reasonable, I'll try to implement it. To be honest it seems to me that it would be annoying for most users, to show the inspection GUI after each save. But as an off-by-default option for specific users, why not I guess.
Teiva Harsanyi
@teivah
well, the best option would be to not have this new window showing up
I mean the perfect scenario would be I save then I see directly in the code editor the potential issues
Jakub Beránek
@Kobzol
right, that makes sense
Teiva Harsanyi
@teivah
but thanks at least it's helping me a lot
Jakub Beránek
@Kobzol
I created an issue: intellij-rust/intellij-rust#5542 let's see what the others think :-)