rust-smallvec
anyerror
| rust-smallvec | anyerror | |
|---|---|---|
| 6 | 1 | |
| 1,244 | 4 | |
| 1.9% | - | |
| 7.4 | 5.7 | |
| about 1 month ago | 6 months ago | |
| Rust | Rust | |
| Apache 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.
rust-smallvec
-
I just published my first crate: `identified_vec` - I would love some input! PR's are most welcome.
You might want to check out how popular ecosystem crates do some of these things. Particularly relevant to you are probably crates providing collections, such as smallvec, hashbrown, or indexmap.
-
Cargo error with Git link, is this intended?
# Uses the given git repo when used locally, and uses # version 1.0 from crates.io when published. smallvec = { git = "https://github.com/servo/rust-smallvec", version = "1.0" }
- Linux Kernel 6.1 Released with Initial Rust Code
-
Learning Rust You Need a Cognitive Frame
smallvec
-
Replacements for existing software written in Rust
> the chances for triggering a buffer underflow / overflow exploit are zero
Doesn't the mere existence of unsafe make this untrue? From a quick google I can see at least one[1] so the chances are definitely a lot higher than zero
[1] https://github.com/servo/rust-smallvec/issues/252
anyerror
-
I just published my first crate: `identified_vec` - I would love some input! PR's are most welcome.
You're using an error wrapping crate. I highly recommend that for a library crate you use hand-written error types, this gives users of your library maximum flexiblity in how they want to use your errors. thiserror is a fantastic crate to help with this: thiserror errors are not wrapped in anything, all it does is provides macros to help you build custom error types with a little less boilerplate (the macros emit code which just uses the error machinery from std and nothing else).
What are some alternatives?
modern-unix - A collection of modern/faster/saner alternatives to common unix commands.
frawk - an efficient awk-like language
toydb - Distributed SQL database in Rust, written as a learning project
toipe - yet another typing test, but crab flavoured
clojure-rust-graalvm - An example of Clojure program calling a Rust library, all combined into one executable using GraalVM.
kyun - The worst text editor (yet)
clasp - clasp Common Lisp environment
too-many-lists - Learn Rust by writing Entirely Too Many linked lists
awesome-rewrite-it-in-rust - A curated list of replacements for existing software written in Rust [Moved to: https://github.com/TaKO8Ki/awesome-alternatives-in-rust]
Cargo - The Rust package manager
Cursive - A Text User Interface library for the Rust programming language
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.