The TrapC compiler can avoid most memory-safe-pointer boundary checks by using AI code reasoning
2 years ago by 0xDEADBEEFCAFE to c/programmingcirclejerk
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.
Rowe told us this week — “The thing about union is it is widely used in C for SSO Short String Optimization… more common than I’d thought.”
surely a good idea to let this guy design a C compiler
@programming.dev
Community to talk about enlightened programming takes
Rules:
- read and follow the programming.dev code of conduct
- no flamewars
- mark your unjerks
- only programming related content allowed
- link to the original source
- do not mention this community in places like hackernews, lobste.rs, or the general programming communities on Lemmy where we source jerk material from.
go to feed...
@programming.dev
Community to talk about enlightened programming takes
Rules:
- read and follow the programming.dev code of conduct
- no flamewars
- mark your unjerks
- only programming related content allowed
- link to the original source
- do not mention this community in places like hackernews, lobste.rs, or the general programming communities on Lemmy where we source jerk material from.
go to feed...
Why write dozens of lines of C when you can set the planet on fire to summon an edge case bug generator instead!
save