-
-
-
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.
-
Sadly, IIRC the Nomicon hasn't seen a new release in a while (meaning there's unpublished Github commits at https://github.com/rust-lang/nomicon ), and there are some TODOs scattered throughout the document. For example, https://doc.rust-lang.org/nomicon/send-and-sync.html says:
> TODO: better explain what can or can't be Send or Sync. Sufficient to appeal only to data races?
Coincidentally I happen to have just written about this topic a few months ago: https://nyanpasu64.github.io/blog/an-unsafe-tour-of-rust-s-s...
There exist unofficial tools for counting the number of unsafe blocks in a project: https://github.com/rust-secure-code/cargo-geiger
However a sufficiently determined evil crate can use soundness holes (like fake-static) or macros (like plutonium) to misbehave without visible unsafe.
This is formatted using a program called mdBook, a tool in rust for converting markdown books to HTML: https://github.com/rust-lang/mdBook
> I think linked lists are a great example of something that causes Rust's ownership model to fall apart. I've seen it done with tradeoffs, but it's something that you're best off implementing with pointers and unsafe blocks
It's worth checking https://plv.mpi-sws.org/rustbelt/ghostcell/ and https://github.com/matthieu-m/ghost-collections for an alternate approach that's currently being worked on.
Quite non-intuitive and it has yet to be proven 100% safe, plus it doesn't actually obviate everything you might want to do w/ potentially-aliased pointers, meaning that some desirable patterns are still off-limits - but it has the best chance of working out so far.