The TrapC compiler can avoid most memory-safe-pointer boundary checks by using AI code reasoning

submitted by

https://thenewstack.io/memory-safe-c-trapcs-pitch-to-the-c-iso-working-group/

Turns out we don’t need a borrow checker after all. We can just use vague “AI code reasoning”. This seems highly credible and I’m sure we’re going to see a fully functional compiler and source release within the next 10 decades.

0
1

Log in to comment

Insert image