this post was submitted on 22 Sep 2025
16 points (94.4% liked)

Rust

7656 readers
23 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

!performance@programming.dev

Credits

  • The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)

founded 2 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
EdTheLegendary@programming.dev
kahnclusions@programming.dev
torcherist@programming.dev
16
[SOLVED] How do i fix expected operator (media.piefed.social)
submitted 3 months ago* (last edited 3 months ago) by artiman@piefed.social to c/rust@programming.dev
7 comments fedilink hide all child comments
 

Why can't I open the thing it nags me about an operator but how is that relevant I'm just trying to open the thing

you are viewing a single comment's thread
view the rest of the comments
[–] artiman@piefed.social 7 points 3 months ago* (last edited 3 months ago) (2 children)

Thank you're a lifesaver, IDK about the error message on the top didn't configure much except nord-night theme must be a bad design choice on helix's part

[–] syklemil@discuss.tchncs.de 7 points 3 months ago

fwiw if you do a cargo build you should be able to see the error messages in the correct context. If I replicate line 25 in a little test project and run cargo build I get

error: expected one of `.`, `;`, `?`, `else`, or an operator, found `{`
 --> src/main.rs:4:43
  |
4 |     let guess: u32 = guess.trim().parse() {
  |                                           ^ expected one of `.`, `;`, `?`, `else`, or an operator

error: could not compile `unacceptable-rs` (bin "unacceptable-rs") due to 1 previous error

If I try this with a blank helix config I don't get any of the text output from rust-analyzer at all, just the three dots indicating there's a problem there, so it's unlikely it's a bad design choice on helix's part.

[–] hollyberries@programming.dev 7 points 3 months ago (1 children)

Inline diagnostics was implemented earlier this year, and is still not enabled by default (likely to prevent breaking existing configs). The changelog is from January of this year:

https://helix-editor.com/news/release-25-01-highlights/

You can set it up here, and is straightforward:

https://docs.helix-editor.com/editor.html#editorinline-diagnostics-section

[–] trevor@lemmy.blahaj.zone 2 points 3 months ago

As an avid Helix user, thank you for linking this! I had no idea this was available, nor that I wanted it in the first place, but now I do.