kuchiki
DISCONTINUED
futures-rs
Our great sponsors
kuchiki | futures-rs | |
---|---|---|
3 | 11 | |
466 | 5,193 | |
- | 1.1% | |
3.4 | 8.5 | |
about 1 year ago | 11 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.
kuchiki
- RIP Soup
-
What sort of mature, open-source libraries do you feel Rust should have but currently lacks?
Btw did you look at https://github.com/kuchiki-rs/kuchiki?
-
Are there any rust libraries implementing a CSS-like language?
You could use https://lib.rs/crates/cssparser + https://lib.rs/crates/selectors - or, if you are willing to convert your tree to DOM just for querying, there are other libraries like https://lib.rs/crates/simplecss, https://lib.rs/crates/nipper, https://github.com/kuchiki-rs/kuchiki or https://github.com/khvzak/victoria-dom
futures-rs
-
Which async channel is best?
So this is actually better than true fairness (true fairness would lead to deadlock if a sender is forgotten). It is a pity that the there does not seem to be resources that document this design. There is this old thread where Carl provides some background, but I found it personally a bit hard to follow.
-
Async cancellation: a case study of pub-sub in mini-redis
Is this still true after it switched to using FuturesOrdered?
-
I don't really understand how I'm supposed to use async
Done.
-
What crates would you consider essential?
futures
-
Async Rust in Practice: Performance, Pitfalls, Profiling
Here is the PR: https://github.com/rust-lang/futures-rs/pull/2551
Yield = wake the `waker_ref`. Avoiding the yield would be clone().wake().
That said, "poll immediately" isn't actually a thing nor was it ever a thing except in incorrect implementations.
-
What sort of mature, open-source libraries do you feel Rust should have but currently lacks?
Rust lacks an implementation of ReactiveX. futures/futures-signals seems to be the the ecosystem equivalent but I'm sure there'd be a lot of interest in an actual implementation.
-
futures 0.3.9 released with big improvement in compile time
Also, we plan to give users more control in the future. See https://github.com/rust-lang/futures-rs/issues/2207, https://github.com/rust-lang/futures-rs/issues/2295, etc. for this
What are some alternatives?
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
async-std - Async version of the Rust standard library
carboxyl - Functional Reactive Programming library for Rust
mioco - [no longer maintained] Scalable, coroutine-based, fibers/green-threads for Rust. (aka MIO COroutines).
tangle - Deprecated - Use https://github.com/alexcrichton/futures-rs instead
coio-rs - Coroutine I/O for Rust
LiteDB - LiteDB - A .NET NoSQL Document Store in a single data file
json-rust - JSON implementation in Rust
rxRust - Rust implementation of Reactive Extensions.
memberlist - Golang package for gossip based membership and failure detection
differential-datalog - An in-memory incremental Datalog engine based on Differential Dataflow
thiserror - derive(Error) for struct and enum error types