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 @spodlife
I imagine `Instant::now()` uses the wall-clock, and thus it can go back in time :(
1
Today's favourite commit message: "chore: Correct potential panic should the installer time travel into the past" The things I do for the @rustlang installer.
1
6
Ugh, halfway around my run today and my calves started to threaten cramps. 10km of walk/try-run/nopenope/walk later and I'm home
2
Replying to @imperioworld_
Okay sounds like it has potential, I'll put it on the list :D Thanks for persisting :D
1
Replying to @imperioworld_
Specifically my difficulty is that I often simply 'freeze' up and can't get my hands to do what they need to on the game, rendering action sequences a bit difficult. I failed quick time events on Detroit:BH despite being on 'easy' mode. I failed them a *lot*.
2
Replying to @imperioworld_
That looks to be a run+shoot type game which is not really what I want. Have I misunderstood the high action rapid moving trailer video?
1
Finally I played Detroit: Become Human through. And I am massively saddened that in the end my attempt to make choices was entirely derailed by my inability to handle 'Quick Time Events' - I was trying to play a story game, not a twitchy thing. Oh well.
1
2
Replying to @jmtd @nineinchnails
You look almost sheepish there, like you've been caught doing something naughty and been told "show the class what you were doing Jon!"
1
1
And we'll miss you Tim. Though when parkrun starts up again, if I'm not too fat to get out of the front door, we shall meet up and you can roll me around the park :D
I recommend the use of tweetdeck which renders twitter actually usable by rolling back a lot of the idiocies.
3
I 100% endorse this idea, but sadly I also 100% expect that the RFC for it would permit "conforming" implementations to choose to ignore it for commercial reasons. *GRUMP*
1
I woke up this morning to realise I was "preaching Rust" at someone who has done it for much longer than me. Whoopsie :D
1
Replying to @nick_r_cameron
My gut feeling is "No because OwnedFoo is not a smart pointer to a Foo" I'd probably lean toward an `impl AsRef<[_]> for OwnedFoo` or else a `pub fn borrow(&self) -> Foo<'_>` Deref requires that the implementing type "contain" the target.
1
1
Replying to @fanf
Is this going to mean we now can't upgrade our CPUs without having to reinstall the OS?
Oh hang on, reduce allocations, hrm. If you want async, surely you're taking an `impl AsyncWrite` though?