I'm just trying to grok what you actually need in terms of data. Is it that for each entry in the list you want (prev,this,next) where at the start that'd be (None,entry,Some(next)) and a the end it'd be (Some(prev),entry,None) ?
I repeat, the ideal information for this to show me is the *charge rate* in *kW* and even better would be to provide a graph over time. percent-per-hour is worthless and confusing, as is miles-per-hour.
Well yes, but the UI is awful. What you want is "I'm charging at x kW now, I will begin throttling after y kWh" or similar. Ideally just give you a graph and you can learn. Bad predictions are just microsoft progress bars all over again.
I certainly wouldn't expect it to take over 2h if it's charging at over 50%/hr.
All I want is "You're receiving X kW right now, averaging Y kW across the charge so far. The battery could take Z kWh more before it's full" type statements.
That does go some way to settling my nerves on this. I can only hope I see more people with this kind of view than the horrorpile of that thread about blocking.
please tell me this isn't serious. I was considering nixos as a new home after debian resoundingly failed to condemn the fsf/rms debacle, but I couldn't join a community which was anti-inclusion.
this is just a simple MVP that essentially gives you a `top(1)`-like view of all the async tasks currently running on a @tokio_rs runtime. we've got a *lot* more planned for future iterations...so if this is something you're into, come help out at github.com/tokio-rs/console!
We're trying out a another beta release of Rustup (@rustlang installer) and we'd like testers to have a go with it if they had issues with 1.24.1 allocating memory in their CI. Details here - internals.rust-lang.org/t/seโฆ