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.
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.
Can we trust #opensource when it matters?
We've been working to build confidence in #FOSS in critical settings over the last few years.
Read about our 2018 study with BMW safety expert Lukas Bulwahn, looking at a key aspect of #linux kernel behaviour:
codethink.co.uk/articles/202β¦
10
1
3
Daniel Silverstone ππππΒ² π³οΈβππ¬π§ retweeted
Google wrote a style guide on writing inclusive documentation:
developers.google.com/style/β¦
It's a good doc but seems like giving up "sanity check" and "crazy" will/would be hard. I'll at least think about it a bit more when I use those terms, though.
In 2014, after being named Teacher of the Year, my supervisor told me if I said I was gay in public I would be "shot in the head."
I was told I would be fired if I did not bring her all of my private mail from home to read. (more)
Several of you have asked me for a Crust of Rust on smart pointers (Arc/Rc/Deref) and interior mutability (RefCell/Mutex/Cell) in @rustlang, and I think it's about time. Let's do a stream on Wednesday at 8:30p UTC (everytimezone.com/?t=5ee95d0β¦) as usual. Come one come all! πΊπ¦
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.