The TrapC compiler can avoid most memory-safe-pointer boundary checks by using AI code reasoning
The TrapC compiler can avoid most memory-safe-pointer boundary checks by using AI code reasoning
thenewstack.io
Memory-Safe C: TrapC's 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.
