That's what's worse, this isn't an FFI interface. It's entirely within rust. And in a From impl so the usage isn't even obvious from the call site.

The mechanisms that are being abused are normally used for interfacing with C code where the concept of a shared or mutable reference doesn't exist (just a raw pointer).

It's converting a shared reference (&'a) to a mutable reference (&mut 'a), which is undefined behavior in rust. There can be many shared references but only one mutable reference. This can cause the compiler to produce the wrong code. It might work in one version of rust and break in a future update

Reminds me of when my team went on a boat ride tour of the Golden gate bridge. All we could see were the bases of the towers. Above us was completely gray.

solve my concerns with build-time vulnerabilities.

I've started learning how to do development in containers. It doesn't make me feel completely safe, but at least a bit more secure. My biggest wishes are that build.rs can be deprecated/removed in the future, and proc macros run in sandboxed wasm environments (or similar). It would at least 1/2

I'm not sure where they're getting it from, but I've done that before in my projects to limit the scope of traits to avoid dealing with name conflicts.

Sorry about the misunderstanding. I interpreted the coworkers comment as all the coworkers in the building.

Oh I just noticed she's on bluesky @perrikaryal.bsky.social

You might want to get in touch with Perrikaryal on YouTube somehow for advice. She plays video games that way.

The article describes that they're already trying to do what you're asking for. Though I don't agree with saying people should be arrested for not identifying the caller. Not everyone in that building is going to know who made the call.

You should read the article

The terms of service is missing the copyright link:
"DMCA/Copyright Policy. Please see Skylight Social’s Copyright Policy at ADD LINK TO COPYRIGHT for more information."

John Oliver did a show on them 8 years ago youtu.be/GvtNyOzGogc?...

Sorry. I interpreted their response as: people can't leave at all unless they pay $100,000

No, he's saying if they're here and they leave, they can't come back without paying. They're not required to pay to leave.

The footer makes it pretty clear to me: "completely unaffiliated with these AI alignment organizations: but our design agency said their logos would look good on our site"

Definitely check out doc.rust-lang.org/stable/book/ available for free online. I'd also recommend not trying data structures with multiple pointers to the same object (doubly linked lists) or self referential pointers until you're more comfortable with the language.

Check out docs.rs/keyberon. Unfortunately, it doesn't have all the features that QMK has. But it does get close