ST-analyzer | Simulation Trajectory Analysis for Molecular Dynamics

Unlike JavaScript, semicolons are not syntactically optional in Rust. Thus, leaving them out is a syntax error, not just a matter of style, and rustfmt (the standard Rust code formatting tool) doesn't ever attempt to fix any syntax errors, no matter how “obvious” they might be — if it reads a file with errors it will not make any formatting changes.

(I don't know if there's a way to get rust-analyzer, vim, or VS Code to auto-insert semicolons as a matter of editing rather than formatting.)

The mismatched type error is because the type of term is explicitly specified as u32, and the first match arm is implicitly returning u32, but the second match arm is returning the unit value (). There are only a few ways to exit a match expression, and here you will either need to return a u32 (which you probably don't want to do), or you can call return to exit from the function, or call panic!() to terminate the program. The continue keyword can only be used inside of a loop, but not matches. There is no equivalent to break from C switch statements unfortunately.

If you didn't want to return from the function right away, you could rewrite this to store the Result returned by parse(), and then use an if let statement to check for an error, but it would likely be better to make a function that can be returned from, which has the match statement in it, and then calling that function from main(). Since the Rust compiler uses aggressive optimizations (at least when compiled with --release), it might actually eliminate the function entirely, so using lots of functions doesn't have the same penalty as it would in C

You're looking for parameter hints in this case. The function for which you want to display hints also needs to have more than one parameter.

Make sure that the setting is enabled:

Settings (UI)

This feature does exist in rust-analyzer, but it needs to be enabled explicitly. To enable it, you need to add the following to your keybindings.json:

Problem is I don't see errors when I type, only after I save.

Rust-analyzer does not support real-time linting (yet?).

In short, rust-analyzer essentially runs cargo check. For small projects this can be quite fast. However, as project sizes increase, this can take significantly more time, which makes it unfeasible to check in real-time.

See also issue #4185 and "Drawbacks" on the "First Release" post.

The next best thing you can do (as you already know), is to use "check on save":

This is a bug in rust-analyzer. For now, you can disable the warning in your settings.json:

Looks fine to me when documented via cargo doc with Rust 1.48.0:

The geo-offset crate implements the Offset trait for geo::Line, not geo_types::Line (src - search for geo::Line). So even so geo::Line is just a re-export of geo_types::Line, the rust compiler doesn't see this deep and only knows about the Offset implementation for geo::Line.

Browsing docs.rs a bit, I found that type sqlx::Query does not even have finalizers other than fetch. As for sqlx::query_as, the trait I was looking for was called PgQueryAs, which actually contains fetch_all, fetch_optional, fetch_one, etc. And adding use sqlx::postgress::PgQueryAs fixed the problem for me.

Despite that, I still don't know a solution for evaluating macros to get decent types in my IDE.