-
-
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.
-
regex
An implementation of regular expressions for Rust. This implementation uses finite automata and guarantees linear time matching on all inputs.
-
It has 2 mature implementations - rustc and rust-analyzer. Tongue-in-cheek aside, there is one other impl in the works - gcc-rs. The reasons cited for people wanting an alternate implementation have never made sense to me. They're trying to shoehorn C/C++ thinking everywhere they go. I think languages don't need a second implementation as long as the first one is free, open source and has a team of maintainers with bus factor > 1.
On top of that, notice that the question is asked about "personal" or "hobby" projects. Those mean different things to different people. Technically, for example, the regex crate is my hobby project because I work on it exclusively in my free time. Does that mean it actually is a hobby project? I imagine most folks hope not! On the other hand, my now defunct nfldb project was also a "hobby" project for the exact same reason, yet it was held together by bailing wire and duct tape.
[dependencies] regex = { git = "https://github.com/rust-lang/regex" } Or from a specific file in your computer like this:
If they aren't, it is extremely broken for a lot of uses cases see the issue tracker. It doesn't inspect/resolve the dependency graph the same way cargo build|test does.
Then don't use cargo. rustc is quite a smart compiler, and it's actually quite easy to assemble your own dependency trees with something like make or tup. It's just that nobody distributes their Rust code in that way... but you're free to, if you want.
Meaning, storing a lot of things in the same block of allocated memory? Vec is a thing, you know. There's also a bump allocator library.