There have been multiple accounts created with the sole purpose of posting advertisement posts or replies containing unsolicited advertising.

Accounts which solely post advertisements, or persistently post them may be terminated.

zero_spelled_with_an_ecks ,
  • C
  • C plus plus
  • C plus plus plus plus
  • C plus plus plus plus plus plus plus plus
  • C plus plus plus plus plus plus plus plus plus plus plus plus plus plus plus plus
dosuser123456 ,
@dosuser123456@lemmy.sdf.org avatar

theres also c+

mkwt ,

There’s also D. You could just upgrade to D.

magic_lobster_party ,

It’s so good it got not only one, but two standard libraries.

sukhmel ,

That’s a transfinite induction

expatriado ,

always wanted to C in the 4th dimension

StrongHorseWeakNeigh ,

TessaraCt

lily33 ,

TesseraC+

marcos ,

That’s a HyperCube.

xmunk ,

I’m waiting for the marvel cinematic universe movie about filling out TPS reports and preparing for Y2k… it’s guaranteed to do better than Black Adam.

lukecooperatus ,
@lukecooperatus@lemmy.ml avatar

Wasn’t that the Loki show, where all of time is run by a boring dystopian corporate bureaucracy?

Now that I think of it, I guess you’re right, that show probably did do better than Black Adam.

AlexisFR ,
@AlexisFR@jlai.lu avatar

T-C-ract

RacoonVegetable ,

https://reddthat.com/pictrs/image/cecb41da-2243-4991-b3c0-904a8ddc4200.jpeg

30p87 ,
@30p87@feddit.org avatar

Skeleton on bank with caption “waiting for hello world to compile 0x0a (cargo needs 69420 dependencies which need to be compiled on the fly, because fuck you, that’s why”

PlexSheep ,

It’s not that bad, besides who cares with machines being as fast as they are nowadays?

30p87 ,
@30p87@feddit.org avatar

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.

ssm ,
@ssm@lemmy.sdf.org avatar

https://lemmy.sdf.org/pictrs/image/69fd3b9a-a612-4d02-86e0-df61b2a04687.png

CanadaPlus ,

Change is hard.

ZILtoid1991 ,

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.

sukhmel ,

Anything that is drop-in replacement for C (or C++ for that matter) is going to be awful because of the same compatibility burden, imo

fermuch ,
@fermuch@lemmy.ml avatar

What about Zig?

ZILtoid1991 ,

Oh boy, Zig is just uglier C++ with memory safety, and it still has those awful header files…

CanadaPlus ,

IIRC it’s garbage collected, so really it’s just a version of Java.

qaz , (edited )

It does not use a GC

CanadaPlus ,

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.

sukhmel ,

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

ZILtoid1991 ,

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.

CanadaPlus ,

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.

ssm ,
@ssm@lemmy.sdf.org avatar

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.

CanadaPlus , (edited )

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.

ZILtoid1991 ,

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.

CanadaPlus ,

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.

JackbyDev ,

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!

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • [email protected]
  • random
  • lifeLocal
  • goranko
  • All magazines
    •