You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That crate was my first Rust project, and the demo is currently broken, not a high priority for me to fix it. I'd be surprised if anyone other than myself really relies on it (though the crate itself is stable and heavily feature-gated... I could move AsyncLoader to a futures module so it's not buried among the other loader stuff)
The real reason - I'd be happy to change that to make it dominator-friendly without being dominator-specific, since it's great having is_loading be a Signal ... not sure how to go about that though... maybe it should return a Stream ?
All in all though, fwiw I'd prefer it in Dominator or futures-signals, feels to me like a very useful primitive like map_ref.
Over time, I've come to find this struct is super helpful in all sorts of general scenarios.
It's defined internally in dominator as an example here:
rust-dominator/examples/async/src/util.rs
Line 27 in fc93afd
I've copy/pasted/exported with permission here: https://docs.rs/dominator_helpers/0.8.0/dominator_helpers/futures/struct.AsyncLoader.html
However, that
dominator_helpers
crate doesn't really do much, and I often find myself importing it for justAsyncLoader
I think it's a good candidate to make part of dominator core
The text was updated successfully, but these errors were encountered: