It's not what you can use that language to do - all general purpose languages are Turing Complete, so what you can do with them is exactly equal. It is about what the language will do for you. Rust compiler will stop you from writing memory unsafe code, C compiler cannot do that.

[–] JackbyDev@programming.dev 1 points 1 day ago (1 children)

Fun fact, some languages are not turing complete and I believe people would still consider them programming languages. They're typically targeted at making mathematical proofs.

[–] nialv7@lemmy.world 2 points 19 hours ago (1 children)

I did say "general purpose". And many proof assistants are Turing Complete actually, such as Lean.

[–] JackbyDev@programming.dev 1 points 18 hours ago

I did say "general purpose".

I did say "fun fact".

[–] qjkxbmwvz@startrek.website 6 points 1 day ago

...are Turing Complete, so what you can do with them is exactly equal.

But they're only equal in the Turing complete sense, which (iirc) says nothing about performance or timing.

[–] Rednax@lemmy.world 4 points 1 day ago (1 children)

But how does the Rust compiler do that? What does it actually check? Could I write a compiler in C that does this check on a piece of Rust code?

C is so simplictic, that if I can write a piece of functionality in C, I must understand its inner workings fully. Not just how to use the feature, but how the feature works under the hood.

It is often pointless to actually implement the feature in C, since the feature already has a good implementation (see the Rust compiler for the memory safety). But understanding these features, and being able to mentally think about what it takes in C to implement them, is still helpfull for gaining an understanding of the feature.

[–] jj4211@lemmy.world 3 points 1 day ago

Could I write a compiler in C that does this check on a piece of Rust code?

Well yes, but that code has to be written in Rust. The human has to follow rules to give the compiler a chance to check things.

C is so simplictic, that if I can write a piece of functionality in C, I must understand its inner workings fully. Not just how to use the feature, but how the feature works under the hood.

I don't think that's particularly more true of C than Rust or even Golang. In C you are frequently making function calls anyway for the real fun stuff. If you ever compile a "simplistic" chunk of C code that you think is obvious how it would compile to assembly and you open up the assembly output, you are likely to be very surprised with what the compiler chose to do. I've seen some professional C developers that never actually had a reason to fully understand how the stack works, since C abstracts that away and the implications of the stack don't matter until you exceed some limitations.