I care, when I need to compile a lot of stuff multiple times on not-as-fast machines. I’ll create a private repo powered by my workstation just for this. For C stuff I don’t need to, because I can just use my workstations power via distcc.
Issue is, Rust is not a drop-in replacement for C. The memory safety features are just one part, and since Rust is also a “weakly” functional language, thus its prefered to write such code with it.
Apparently, I do not RC. I might have been thinking of Nim. A quick search indicates it’s not memory-safe, though. It has a few helpful features to keep errors under control, but that’s it.
I was planning to check it out, but don’t have any experience yet. I thought it is more of a replacement than drop-in replacement, I may have been wrong
D is a mostly drop-in replacement (type renaming and such needed though), and it doesn’t have that issue. D even has a mode called BetterC, where the D standard library and the garbage collector is left out.
Yeah, it’s not a small change. If there was a simpler way to make C memory-safe, it would have been done decades ago. It’s just a different language too, which is fair given how much younger it is.
If there was a simpler way to make C memory-safe, it would have been done decades ago.
We’ve had compile time sanitizers (-fsanitize=blah in gcc/clang) and runtime sanitizers (valgrind) for ages. I don’t know how they stack up against rust’s compile time sanitizers, but it’s something.
About how an Excel spreadsheet with no formulas stacks up against a corporate accounting suite. Valgrind is how you find the bleeding once you inevitably introduce a memory bug. I don’t understand all the fsanitize options, but I’m guessing they aren’t a blanket solution, exactly because memory bugs have still been inevitable.
This thread is making me wonder how many people actually understand what Rust does. It rigorously prevents any form of memory error at all in normal code, and unsafe blocks, where needed, tend to be tiny. It makes C segmentation faults look just as goofy as JavaScript type errors.
D kind of did that (C pointers are still an option, alongside with the preferred dynamic arrays, which has the memory safety features), and once I’ve seen a C compiler fork that retroactively added D-style memory safety features, although they also very much insisted on the “const by default” mantra.
I think this is one of those things where there’s no “kind of”. Pointers were added for a reason, you’re probably not going to implement a database very well without them. If you use them, at some scale you’re inevitably going to have memory bugs. Technically, if you were to only use hardcoded printfs, C is memory safe too.
I once saw an issue someone made for some database and said that they were learning Rust and if the database was rewritten in Rust then they could help contribute!
ARCHETYPE NAME:
The Misunderstood Genius
The digits in the number 31 have the digit sum 4 which resonates with the planet Uranus. 31 is often written as 31/4 where the digit sum is placed after the slash. To understand 31 more in depth we recommend you also read more about the digit sum 4 here.
Me too - maybe because I was distracted by the irony that C# devs are typically the opposite of sharp… Or because it’s MicroShit and I didn’t give a flippin fuck ;)
"Just a heads up that we'll be shipping your machine to the client, since it's the only machine on Earth known to support the software. You're getting the spare machine out of the basement. Super fast Cyrix processor. Looks like it boots to Windows 11 release 3, but they've written it 3.11 for some reason."
This isn’t the evolution of C at all. It’s all just one language and you’re simply stuck in a lower dimension with a dimensionally compatible cross-section.