If you squint at it from the right angle, Capability-Based-Addressing is basically making C memory-safe. Lots of excellent CBA research comes from the CHERI pr

If you squint at it from the right angle, Capability-Based-Addressing is basically making C memory-safe. Lots of excellent CBA research comes from the CHERI project http://www.cl.cam.ac.uk/research/security/ctsrd/ http://www.cl.cam.ac.uk/research/security/ctsrd/ However, they struggle to run lots of very routine C programs; its surprising how many normal programs you run happen to have been written in C and happen to rely on unions and memory unsafety etc! For example, if you read http://www.cl.cam.ac.uk/research/security/ctsrd/pdfs/201503-asplos2015-cheri-cmachine.pdf http://www.cl.cam.ac.uk/research/security/ctsrd/pdfs/201503-... and look at Table 1, you'll see common programs and libraries such as libc and Python which cause trouble for 'memory-safe C'.