Rust should not have provided `unwrap`

This page summarizes the projects mentioned and recommended in the original post on news.ycombinator.com

Our great sponsors
  • Scout APM - Truly a developer’s best friend
  • SonarLint - Clean code begins in your IDE with SonarLint
  • talent.io - Download talent.io’s Tech Salary Report
  • rust

    Empowering everyone to build reliable and efficient software.

    There is a problem here - it's verbose and prone to silent-ish breakage if the surrounding context changes due to e.g. refactors (well, probably not with this tiny example, but you probablu know what I mean). Thankfully, there is also a solution to this problem: https://github.com/rust-lang/rust/issues/90091

    split_array will eventually allow something like the following, which avoids any explicit indexing and will fail to compile if the sizes don't match up:

        struct IVec2(i32, i32);

  • Clippy

    A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/nightly/clippy/

    [Clippy](https://github.com/rust-lang/rust-clippy) has a lint that will check for `.unwrap()` calls; [unwrap_used](https://rust-lang.github.io/rust-clippy/master/index.html#un...).

    It is allowed by default, but you can turn it on in the configuration file.

  • Scout APM

    Truly a developer’s best friend. Scout APM is great for developers who want to find and fix performance issues in their applications. With Scout, we'll take care of the bugs so you can focus on building great things 🚀.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts