-
Clippy
A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
rust-analyzer
Discontinued A Rust compiler front-end for IDEs [Moved to: https://github.com/rust-lang/rust-analyzer] (by rust-analyzer)
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
There’s a little thing with rust - you probably dont want to write a linked list in it (or do entirely too many linked lists to boot). There are almost always better container structures to use.
Are you using clippy by any chance? Clippy has taught me more about how to navigate the Rust language in my own code than reading just about anything else.
Oh, try Rust-Analyzer, too!
Fundamentally, Rust is very much about this sort of "Build a piece using unsafe, wrap it in an API which ensures correct usage, audit the crap out of it using tools like Miri, Loom, cargo-fuzz and/or afl.rs, Valgrind, etc., and then let your safe code rely on it."
Like others have said, you really should start with a simpler project. If I were you, I would follow along with the book. That's where I started, and there are some great little projects in there to get you going. After you've gotten more familiar, you can come back to linked lists and have a much better time.
Did you try the rustlings already?
An invalid value (e.g. reading bool from a memory that contains something other than true or false) is UB. It's unsafe to "produce" such value even if you never inspect it and only ever send it to mem::forget(). (See this PR for an interesting discussion.)