Sure thing but that's not realistic if you work professionally as you might be handed code that 15 other people worked on for a decade before you.

You will not be able to reason about the memory properly, in which case if certain variables are marked with const it will tell future people that this is read-only memory.

On Tuesday, 25 January 2022 at 10:42:35 UTC, bauss wrote:

Yeah, the problem with me is that I almost thing about the most cases when you work alone or with good people but never cases like the one you described. The others did an amazing job explain that to me. That and the fact that humans do mistakes even when they know what they are doing...

Sure thing but that's not realistic if you work professionally as you might be handed code that 15 other people worked on for a decade before you.

You will not be able to reason about the memory properly, in which case if certain variables are marked with const it will tell future people that this is read-only memory.

On Tuesday, 25 January 2022 at 10:42:35 UTC, bauss wrote:

When saying "we would try to avoid working with read-only memory and pointers directly", I mean the language I'm going to create. So yeah, there will be no code from 10 years ago, I'm pretty sure ;)

Aside from the joke, I will keep the fact the a lot of people will work in the same project so having as many protections as possible.