You should add a disclaimer that you are the CEO of Fil-C. /s
In the context of this vulnerability, I doubt memory safety would have made much of a difference.
This is a great reminder though, currently doing a full userspace replacement on my 3D printer and Fil-C might be just what I need for the irreplaceable C parts.
Type confusion, leads to using an object in memory with the wrong type, that means accessing memory with a different layout, like an out of bounds buffer.
So I think memory safety does matter in that case.
In the context of this vulnerability, I doubt memory safety would have made much of a difference.
This is a great reminder though, currently doing a full userspace replacement on my 3D printer and Fil-C might be just what I need for the irreplaceable C parts.