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
- Tweets 12,967
- Following 105
- Followers 493
- Likes 1,386
+1 for 'barcode scanner' which is based on zxing - you just get to use the clipboard to copy stuff around between the scanner and whatever app you want to store info in.
Indeed, I love how when we supported BLM on the recent release, all I can find is people saying "Why don't we support this more widely, rather than only in a release announcement?"
2
Every day I thank whoever that ESR hasn't set his sights on the Rust community. I really feel for the Go community today, they have a toxic malingerer stepping in.
8
I'm sure @rjek could come up with some exim ACLs for our mail frontends.
2
github.com/rust-lang/rustup/โฆ might be a nice light one to get started with. It mostly involves improving an error message and perhaps the code which raises it. If that interests you then say so on the issue and we'll start the process. If not, say here and I'll look for another.
1
I'll have a skim through the issues I've marked as being prepared to mentor and see if I can find a nice one for you
1
Yeah, I can understand that. Go's management of memory makes it a lot easier to grok things which Rust often requires you make explicit. If you have any specific questions or want to have a chat to grok any Rust, let me know, I'm happy to help.
1
And I bet, after a while with Go, it hurt to get it there :D The learning 'curve' with Rust can be a tad sharp.
1
FYI, on a fresh hello world on my laptop (SATA SSD, i7-6700HQ) `cargo build` -> cargo being invoked (rustup proxy time) 12ms. 39ms until cargo invokes rustc (proxy), 10ms until proxy runs rustc real for metadata. 8ms later, rustc run to compile, 11ms proxy 33ms until src read.
1
1