-
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.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
See my RFC https://github.com/rust-lang/rfcs/pull/3100
I agree with the general sentiment, and much of the stuff I build has little activity after an initial phase of getting it "done". However, I'm still around to merge important patches. But in the case of rental, the git repository is archived and most importantly the author has written that "users are encouraged to explore other solutions". Recently users of rental have been facing a future compat lint in rental, and thankfully the maintainer fixed it, but I think their intent of urging users to alternatives remains as immediately afterwards the repo got re-archived.
Here's an interesting discussion, consolidated here. My view is you should use a restricted scope atomic (as best as can be supported) and interact with that through a handler struct. I.e. no global state.
Here's an interesting discussion, consolidated here. My view is you should use a restricted scope atomic (as best as can be supported) and interact with that through a handler struct. I.e. no global state.
If you switch pointers for indirect indexes, then you can quite easily make a purely safe doubly-linked list in Rust. I did that as a learning exercise and called it index_list (github), where all elements and nodes are stored in a vector (for improved locality). In my very short and non-general tests it performed better than the standard LinkedList implementation. It also provide you with an alternative way to iterate over the list with mutable access to its elements. It probably is not at the same level of quality as standard library things, as I'm quite new to Rust in general, but thought the design would be worth consideration in this context.