c projects are required to have a minimum number of memory safety bugs, as a de facto language standard

8:16 AM · Feb 18, 2021

6
11
0
91
Replying to @The6P4C
I thought C programs were entirely memory safety bugs.
2
0
0
10
No, there’s also some memory-safe undefined behaviour
0
0
0
2
Replying to @The6P4C
Not so much required, as guaranteed by language design.
1
0
0
7
incorrect-by-construction
0
1
0
6
Replying to @The6P4C
Having fewer than the minimum is undefined behavior
0
3
0
11
Replying to @The6P4C
they're not bugs, they're features you're thinking of the wrong way. out of bounds array indexing? Free bonus data! dereferenced a null pointer? Party time! Any behaviour allowed now! buffer too small? No worries, there's still space left! You weren't using those bytes anyways.
1
5
0
17
“shared memory” is when you overflow your buffer and “borrow” some from the next variable up.
1
0
0
4
Replying to @The6P4C
It follows from the fact that UBs are de iure in the C language standard.
0
0
0
3
Replying to @The6P4C
If you remove one, a new one springs into existence
0
1
0
3