lobsters__briankung@crustaceanson.theshelf.topM to Lobsters - all tags@crustaceanson.theshelf.topEnglish · 16 days ago[c, security] The Fil-C Manifesto: Garbage In, Memory Safety Outgithub.comexternal-linkmessage-square40linkfedilinkarrow-up11file-text
arrow-up11external-link[c, security] The Fil-C Manifesto: Garbage In, Memory Safety Outgithub.comlobsters__briankung@crustaceanson.theshelf.topM to Lobsters - all tags@crustaceanson.theshelf.topEnglish · 16 days agomessage-square40linkfedilinkfile-text
minus-squarelobsters__pizlonator@crustaceanson.theshelf.topMlinkfedilinkarrow-up1·16 days ago I think the key thing here is that it’s possible. Exactly! I’d expect a 50% overhead to be plausible My estimate is: if no thin pointer annotations are used, ever: 2x overhead if thin pointer annotations are used in anger: less than 50% overhead, maybe even parity score 2 · canonical
Exactly!
My estimate is:
score 2 · canonical