Linux

8043 readers

44 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
Be respectful: Treat fellow community members with respect and courtesy.
Quality over quantity: Share informative and thought-provoking content.
No spam or self-promotion: Avoid excessive self-promotion or spamming.
No NSFW adult content
Follow general lemmy guidelines.

founded 1 year ago

MODERATORS

[email protected]

141

Rust developers are frustrated with Linux C kernel developers. (lemy.lol)

submitted 2 months ago by [email protected] to c/[email protected]

45 comments fedilink hide all child comments

cross-posted from: https://lemy.lol/post/30414136

Mastodon.

Wedson removing himself as maintainer of the Rust for Linux project.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 0 points 2 months ago (1 children)

Is that not what unsafe is for?

[–] [email protected] 2 points 2 months ago

It's what C is for, too.

The point is that there may be cases already where the type system that rust provides its guarantees off the back of is insufficiently expressive. (I say "may be" because there are ingenious qays to use what it does provide, although nonobvious and not necessarily without cost.) If you're using unsafe then it's just an uglier C. I don't think anyone considers the current state of Rust's type system to be the be-all and end-all of expressivity.