|
|
|
|
|
by mirashii
2 days ago
|
|
I've spent some more time over the last day looking at Fil-C more closely, and come to the conclusion that this: > The thing that makes races hard to debug in C or C++ is memory corruption; that doesn’t happen in Fil-C is just blatantly false. It's almost as easy to corrupt memory in Fil-C as it is in C. Type confusion is still allowed. You can still do out of bounds buffer reads/writes as long as they fall within an allocation, so any intra-object stuff, as you might get in common packet or binary file parsing, is still about as unsafe as it was before. |
|