fenix
anyhow
Our great sponsors
fenix | anyhow | |
---|---|---|
19 | 13 | |
562 | 5,049 | |
7.1% | - | |
9.5 | 8.4 | |
about 18 hours ago | 9 days ago | |
Nix | Rust | |
Mozilla Public License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
fenix
-
Use nix-shell or systemPackages
Rustup works as is. Though note that Nix supplants all such toolchain installers such as Rustup, nvm, etc. I.e. instead of Rustup there is fenix.
-
Can rustc generate identical binaries, with the same hash, from the same souce code?
Fenix ( https://github.com/nix-community/fenix ) has tooling or picking a specific toolchain or even nightly. You can then build with the following nix code:
- Fenix: Rust toolchains and rust-analyzer nightly for Nix
-
Annoucing fenix monthly, Rust toolchains updated 1st of every month
Fenix monthly is a new branch similar to the main branch, but only updated on the 1st of every month, for cases where you want to use rust nightly but don't need it to be updated very often.
- Fenix - Rust toolchains and rust-analyzer nightly for Nix
- Show HN: Fenix – Rust toolchains and Rust-analyzer nightly for Nix
-
Why this overlay doesn't work?
The issue should be fixed once the nix-vscode-extension and fenix patches are merged. The latter will happen automatically once CI passes.
-
Have a few questions about NixOS
4. I would suggest Mozilla's Rust overlay or fenix or similar instead of Rustup - that would be more of the "Nix-way" to acquire the toolchain and you can still manage multiple versions. Not sure what the Ruby equivalent is, I don't do Ruby.
-
Oops, I Did It Again...I Made A Rust Web API And It Was Not That Difficult
To follow along, you'll need a stable Rust toolchain. See the install page for instructions to install rustup for your platform. You should prefer this method to your distribution's package manager. If you're a NixOS freak, I recommend fenix.
- Fenix: rust toolchains for all channels and rust-analyzer nightly
anyhow
-
I love building a startup in Rust. I wouldn't pick it again.
Depending on your use case, thiserror and/or anyhow.
-
Why Rust?
There is ? as well as the anyhow(https://github.com/dtolnay/anyhow) crate that deals with long nested result chains.
- Anyhow/src/ensure.rs: Rust macro with 675 lines
-
Is this a good way of handling errors in Rust?
There are crates out there that help you reduce this boiler plate. thiserror is good for creating custom errors and color-eyre or anyhow are good for dynamic errors.
-
Looking for general advice on toy project
Give anyhow a look.
-
Oops, I Did It Again...I Made A Rust Web API And It Was Not That Difficult
I've brought anyhow::Result into scope, making error handling super easy to use. We don't need to specify all our Error types. It can automatically convert any errors that implement std::error::Error, which should be all of them. If an error propagates all the way up to main(), we'll get all the info it's captured printed to stdout.
-
Idiomatic way to return/break if Err/None
Alternatively, if you've got a lot of error types and you're outside a library (so directly in a binary where you don't plan to reuse code elsewhere) you can use anyhow. This gives you an error type you can basically propagate any other error through. On top of that you can attach context information at every return. It's basically a more complicated Result>.
-
Using workspace for modularization is kind of painful?
One approach is to define a separate error type for each crate and then use anyhow, eyre or Box to wrap the error, whever a function can return errors originating in several different crates.
-
Can we please stop downvoting people who dislike Rust?
Have you tried anyhow and thiserror for making it as simple as .context("Message") or ? to type-convert and propagate errors up the call stack?
What are some alternatives?
rust-overlay - Pure and reproducible nix overlay of binary distributed rust toolchains
eyre - A trait object based error handling type for easy idiomatic error handling and reporting in Rust applications
nixos-flake-example - This is a demo NixOS config, with optional flakes support. Along with notes on why flakes is useful and worth adopting.
color-eyre - Custom hooks for colorful human oriented error reports via panics and the eyre crate
Nightlies - Nightly builds for DuckieTV
thiserror - derive(Error) for struct and enum error types
nixpkgs - Nix Packages collection & NixOS
rust - Rust language bindings for TensorFlow
nix-cargo-integration - Library to easily and effortlessly integrate Cargo projects with Nix.
structopt - Parse command line arguments by defining a struct.
lazy-static.rs - A small macro for defining lazy evaluated static variables in Rust.
cargo-edit - A utility for managing cargo dependencies from the command line.