TehPers

Saw Diesel mentioned, but also wanted to throw SeaORM out there. Might be worth looking into as well.

No, the attribute is unsafe. An unsafe function is marked unsafe fn.

Also, unsafe by itself just means there are invariants that must me manually upheld to avoid unsound behavior. If those invariants are upheld, then it doesn't matter if it's unsafe.

#[unsafe(export_name = "my_super_duper_function")]
pub fn foo() {}

I would recommend reading up some materials on FFI in Rust if you're interested. Calling functions in Rust from C and in C from Rust (or even languages other than C) is both extremely common and a primary usecase of the language.

I never need to send files or data from my phone to someone else's phone. All the files I care about are on my PC.

I'm not saying AirDrop or Quick Share are useless. I'm saying I don't use them, but do understand they're used, and I'm glad the support exists ~~now~~ soon.

For a feature I'll likely never use, I couldn't be happier this happened. Great job, EU!

Yep. This was the difference between a silent, recoverable error and a loud failure.

It seems like they're planning to remove all potential panics based on the end of their article. This would be a good idea considering the scale of the service's usage.

(Also, for anyone who's not reading the article, the unwrap caused the service to crash, but wasn't the source of the issues to begin with. It was just what toppled over first.)

is Windows a drug?

No. Drugs can give you a good time. Windows can't.

Ths survey reminded me of a bunch of awesome features that I forgot were stabilized, many of which I can use in current projects lol. I know that wasn't the intent, but it's a nice side effect of filling it out I guess.

s/OpenBSD/TempleOS

most dedicated electric cars come with a shit ton of sensors which give all that juicy data to third parties.

This is true of all cars, not just electric cars. Plus, this is not an argument against EVs. It's an argument for privacy.