gust
snafu
gust | snafu | |
---|---|---|
2 | 2 | |
6 | 1,271 | |
- | - | |
9.0 | 8.0 | |
4 months ago | 25 days ago | |
Rust | Rust | |
MIT License | 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.
gust
-
Pragmatically handling errors in Rust
This tutorial helped me improve my understanding along with the Book and the docs. In a beginner project I've been working on--a tool to make grocery lists--I've tried to work on my understanding of using Result and the ? operator. Right now I'm using Box in my different functions to pass down error messages to main() in case there's something wrong, and using something like this code snippet to give more helpful errors to a user where necessary: ``` src/lib.rs
-
Beginner project: a grocery list maker using `serde` to parse JSON
I wrote a typical first project type application called grustery-list, which I've been using to put grocery lists together. It updates a library of groceries we regularly buy, a library of recipes we often make, saves a most recent grocery list in case I just want to update a list I made earlier, and prints out a grocery list. I've been using Element to copy and paste my list and send to my phone before we go shopping.
snafu
-
Modular Errors in Rust
I encourage people to check out my SNAFU crate [1]. I encourage creating many distinct error types (usually enums but also structs) and composing them. So much so that I advocate that you never create one specific error in more than one source location. That means that the collection of error types produces a unique trace through your program, uniquely identifying the source of the error with no runtime cost (compare this to a runtime-collected stacktrace / backtrace).
[1]: https://docs.rs/snafu/
-
Announcing Rust 1.58.0
Yes, all procedural macros are inherently unhygienic. This has even bitten us once before.
What are some alternatives?
serde-wasm-bindgen - Native integration of Serde with wasm-bindgen
rust - Empowering everyone to build reliable and efficient software.
rust-experiments - Small experiments in writing Rust programs to perform specific tasks
miette - Fancy extension for std::error::Error with pretty, detailed diagnostic printing.
serde-ndim - Serde support for n-dimensional arrays from self-describing formats
enum-code - derive(Code) simplifies error handling by providing an easy-to-use enumeration of error codes
classi-cine - A filename based interactive video tagging tool.
deno - A modern runtime for JavaScript and TypeScript.
rust-obs-plugins - A safe wrapper around the OBS API, useful for creating OBS sources, filters and effects.
unsafe-code-guidelines - Forum for discussion about what unsafe code can and can't do
alkonost - Simple spam detector for YouTube chats with different UI options