The Garbage Collector

« first day (520 days earlier) ← previous day next day → last day (126 days later) »

Eldritch Conundrum

14:21

What are languages with good support for enforcing that a piece of code does no allocations?

5 hours later…

New Posts

19:04

Q: Analysis of methods to ensure memory safety

Abstract Ensuring memory safety is a core facet of modern programming language design. Memory safety can be guaranteed in many different ways. For the purposes of this question, I am defining memory safety as the prevention of the following bugs: Note that a language may provide an 'unsafe' worka...

Seggan

19:22

@NewPosts i honestly dont know what to say to this question

Eldritch Conundrum

19:48

it kinda makes sense

but there's not much to say

1 hour later…

Michael Homer

21:19

I am a bit puzzled to see value overflow and underflow identified as memory safety bugs on their own

Eldritch Conundrum

21:56

true... I didn't even notice. maybe memory safety was confused with C's UB on signed ints

Michael Homer

They can definitely contribute to e.g. a buffer overflow, but those were mentioned already

Dannyu NDos

22:24

I'm langdeving, and this struct shall serve as the base type for polymorphism:

struct Object {
    consteval Object() noexcept = default;
    consteval Object(const Object &) noexcept = default;
    consteval Object(Object &&) noexcept = default;
    virtual consteval Object &operator = (const Object &) noexcept = default;
    virtual consteval Object &operator = (Object &&) noexcept = default;
    virtual constexpr ~Object() noexcept = 0;
};

Yuck. I cannot rant more for bloatedness of C++.

1 hour later…