Mostly Grey former ginger with a preference for Rust. Leads wg-rustup, sorry about the mess. He/Him or They/Their Now @kinnison@fosstodon.org too

Manchester
Joined December 2008
Filter
Exclude
Time range
-
Near
Replying to @fanf
itertools is love. itertools is life. (oh, and rayon too, rayon is happiness)
3
Replying to @fanf
This isn't *quite* what you're after, but it's close (Option,Option,Option) rather than (Option,value,Option) -- play.rust-lang.org/?version=โ€ฆ
1
1
Replying to @fanf
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) ?
1
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.
Replying to @fanf
If I knew the shape of what you had and what you wanted, I might be able to make a suggestion.
1
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.
Replying to @dickontoo
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.
Replying to @fanf
I keep wanting if/else expressions in other languages because ?: is so easy to misread :D
I thought that was what it was meant to be. i.e. only first-time contributors get caught with this.
1
2
Replying to @grhmc
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.
2
Replying to @rjek
We made some expensive earbuds which will fall out of your ears as they have no limits on distance from your head when "in use"
2
Replying to @grhmc
That's my hope, but is there anyone who is nominally able to speak on behalf of the project to say that. Can someone state "This is our position" ?
5
Replying to @grhmc
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.
1
2
This looks so awesome
Replying to @mycoliza
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!
1
Replying to @kianryan
I'm sure it'll turn out that this one session it approved of was actually a really bad idea in the long term :D
1
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โ€ฆ
1
1
Replying to @fanf
I'm glad you're getting there :D let me know if you want other Rust hints :D
1