The empire of C++ strikes back with Safe C++ blueprint

Re:The empire of C++ strikes back with Safe C++ blueprint by 3836293648 on Monday October 21, 2024 @11:42AM (#41905355)

"affording" GC is absolutely a thing. You're measuring the wrong thing. It's primarily about latency, not throughput, and GC can only go head-to-head on throughput.

Secondly you have places where you don't have dynamic memory at all which you're also conveniently ignoring.

[ Parent | on HN ]

Re:The empire of C++ strikes back with Safe C++ blueprint by pizlonator on Monday October 21, 2024 @11:57AM (#41905492)

Fil-C has a concurrent GC. It doesn’t stop your program, ever.

If your C code doesn’t dynamically allocate then it won’t create any GC load in Fil-C.

[ Parent | on HN ]

Re:The empire of C++ strikes back with Safe C++ blueprint by riku_iki on Monday October 21, 2024 @12:43PM (#41905907)

> Fil-C has a concurrent GC. It doesn’t stop your program, ever.

what about performance/throughput compared to when you allocate stuff on stack?

[ Parent | on HN ]