Happy 10th anniversary of stable #rustlang 🎊

Don't. Make. Me.

Tense moments playing #piglets

@aperezdc @fasterthanlime But would having fewer dependencies really solve that? And I really would like smarter sharing of build artifacts, but between feature flags and Rust coping with the “diamond dependency” problem you probably aren’t really compiling the same thing dozens of times, just a thing with the same name. Though it should still be possible to improve even that scenario.

@twilwel @BM_Visser I assume these numbers are not by number of inhabitants. Which wouldnt’t make too much sense anyway. So larger countries have advantage over smaller and more densely populated countries.

@tenderlove Happy bithday!

@b0rk i don’t know if they thought about oneline history. But the convention is that the first line of the commit message is the subject. That should probably be the title of the merge/pull request.

The fact that it’s a merge is more a detail and some random request-id that has no beating without some external system is more something for the footer of a request. Or at best a short preamble like “Pull #123: <title>”.

@b0rk The lack of good oneliner support has more to do with the merge message generated by Github and Gitlab then with how merges history is formatted.

@KFvMalssen @BM_Visser So energy consumption hasn’t changed significantly (and thus production hasn’t really changed, due to them needing to be balanced).
But in a powerplant scenario production load is introduced in the core of the network, whilst in the solar proposition production load comes from the edge.
So we’d probably need a heatmap showing the load across the network and not the total load (as it had barrly changed) or the composition of that total load.

@calcopiritus @hatchet That way you can pass a reference or anything that can be turned into a reference as an argument. So the caller can supply a &T, Box<T>, Rc<T>, Arc<T>, … (I dont’t know if there is a blanket impl so that even T itself will work.