this post was submitted on 19 Mar 2024
0 points (NaN% liked)

Programming

16977 readers
187 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS
 

Python is memory safe? Can't you access/address memory with C bindings?

top 16 comments
sorted by: hot top controversial new old
[–] Dark_Arc@social.packetloss.gg 0 points 5 months ago (1 children)

Python is memory safe? Can't you access/address memory with C bindings?

You can do that in basically any language. Rust even has the ability to break out of its safeguards and write unsafe Rust code.

"Memory safety" in this context is more about the defaults and how easy it is to write unsafe code accidentally.

[–] Traister101@lemmy.today 0 points 5 months ago (1 children)

Unsafe Rust really just let's you play with pointers

This is the entirety of what Unsafe Rust allows

  • Dereference a raw pointer
  • Call an unsafe function or method
  • Access or modify a mutable static variable
  • Implement an unsafe trait
  • Access fields of unions
[–] declination@programming.dev 0 points 5 months ago* (last edited 5 months ago) (2 children)

I'm still onboard with rust as being better than C, however...

My understanding is that it is considerably harder to correctly write unsafe rust than it is to correctly write c, because if you accidentally violate any of safe rust's guaranteed invariants in an unsafe block, things go bananas.

[–] BatmanAoD@programming.dev 0 points 5 months ago

That's true in C as well, though. This is what people mean when they say things like "undefined behavior can result in time travel".

The difference is twofold:

  • Rust's rules for valid unsafe code are not completely formalized yet. This means that there are open questions about whether particularly complex patterns in unsafe code will be guaranteed by future versions of the compiler to be sound. Conversely, the C and C++ spec are generally sufficient to determine whether any particular piece of code has undefined behavior, even if actually analyzing it to find out is not possible automatically using existing static analysis tools.
  • Because safe Rust is so strict about what it permits, the compiler is able to make more aggressive optimizations; in theory, this could indeed cause undefined behavior to be "worse" at runtime than a comparable situation in a globally-unsafe language. I'm unaware of any actual examples of that phenomenon, though.
[–] Traister101@lemmy.today 0 points 5 months ago* (last edited 5 months ago) (1 children)

Yes Rust is harder to write than C, that's basically by design as it's due to the statically guaranteed memory safety. That's pretty magical. C doesn't have that and neither does C++ even with smart pointers and such. Rusts unsafe keyword is poorly named, what it actually does is tell the compiler that you the programmer guarantee Rusts rules are upheld within the unsafe block.

For example

Access or modify a mutable static variable

That is a global, that's incredibly hard to impossible to statically prove it's safely done, so you have to do it in an unsafe block. So you violating Rusts rules within an unsafe block is actually using the unsafe block wrong. That's not what it's for

[–] Fal@yiffit.net -1 points 5 months ago (2 children)

Yes Rust is harder to write than C

I would totally argue with this. Rust is way easier to write than C

[–] vext01@lemmy.sdf.org 0 points 5 months ago (1 children)

I agree for the most part, but writing data structures with shared mutable state can be a total pain in Rust.

[–] Fal@yiffit.net -1 points 5 months ago (1 children)

How so? That's like, the thing that makes rust awesome to write.

[–] vext01@lemmy.sdf.org 0 points 5 months ago (1 children)

It's hard to get those kinds of data structures through the borrow checker.

Try writing a doubly linked list.

[–] Fal@yiffit.net -1 points 5 months ago

It's because it's hard to make them correct. It's not any harder to write it in rust than in C. Just C lets you do it wrong

[–] Traister101@lemmy.today 0 points 5 months ago (1 children)

I'd probably say it depends but I'm no Rust expert and I have no direct experience with C (though quite familiar with C++).

Basically I'd expect writing C to be easy, but not safe. IE you can quickly and easily write C that compiles but has runtime issues. Rust for the most part will catch everything but logic issues during/before compilation meaning once the program runs you'll have very high confidence in it's runtime behavior leading to time spent "fighting the compiler" instead of figuring out wtf is going wrong at runtime.

[–] Fal@yiffit.net -1 points 5 months ago

IE you can quickly and easily write C that compiles but has runtime issues.

So what's "easy" about it then? Just getting something to compile? That's not a very good measure of "easyness".

[–] qprimed@lemmy.ml 0 points 5 months ago* (last edited 5 months ago) (2 children)

heh! so glad I intentionally avoided C++ from the get-go. C when I want to blow some fingers off quickly, python when I want to stroll down a country lane picking flowers. there is no in-between ;-)

[–] solrize@lemmy.world 0 points 5 months ago (1 children)

C++ is nicer to use than C, and with currently preferred style it's safer, though not safe in the way Python is.

You might also try Go and Ada. I confess to not having clear understanding of how Rust beats Ada or vice versa. There are very few people really knowledgeable about both, who have addressed this afaik. I can say coding in Ada feels clanky but very solid. Idk yet about Rust.

[–] Fal@yiffit.net -1 points 5 months ago

Coding is rust is amazing. It feels so right

[–] Fal@yiffit.net -1 points 5 months ago

Why not choose rust instead of C, then you can trivially write python bindings directly to your rust https://pyo3.rs/v0.21.0-beta.0