@wcrichton y is saying "I'm the new boss here. Anybody wants to talk to x? They gotta go through _me_."
In the first example, z correctly asks y's permission to talk to x.
In the second, z fails to ask permission. It tries to go around y, and gets shot by the compiler for insolence.
Programming language documentation tools usually include a link to the source code being documented. It's often handy! What would you say is the main purpose(s) of that feature?
For years, Bulletproof TLS and PKI has been _the_ book to read for, well, TLS and PKI. Now the second edition is out! Go grab a copy. You won't regret it.
https://t.co/D0vO6X9UVj
I was curious - how much of my Wordle game is luck? Were my guesses good at each step? So I made a post-game analyzer: https://t.co/U00eztsYt8.
Here's a screenshot analyzing a completely hypothetical game of Wordle (not a spoiler):
Rust trait coherence: You can't create a headcanon that struct Foo and trait Bar from another crate are in a relationship, because you don't own that IP. You're only allowed to ship Foo/Bar if one or the other (or both!) is your OC.
Rust has these things called the Orphan Rules which people find confusing but I have solved this problem for everyone:
The only fanfics allowed in rust are self-inserts.
I'm excited to join the rustdoc team! I've been working on speed and usability improvements to the JS and HTML. The team has been so awesome and supportive. https://t.co/6EAX5jBOrM
Houses are basically tools for keeping water out, but we punch lots of holes in them to bring the water inside the house. This demonstrates the futility of perimeter-based security.