Shifting from C and C++ to memory-safe programming languages like Rust is gaining ground
Shifting from C and C++ to memory-safe programming languages like Rust is gaining ground
In February, Josh Aas from Internet Security Research Group, Daniel Stenberg from curl, and I (from hyper and Amazon Web Services) hosted a joint webinar to discuss memory safety and the internet, and how using hyper in curl can help make the internet safer. Because curl is open source and permissively licensed, it is found […]
Will Rust still exist, and have proper support, 10, 20 or even 30 years from now? We’ve been asked this quest…
Not everything will be rewritten in Rust, so C++ must become safer, and we should all care about C++ becoming safer.
Memory safety is a property of some programming languages that prevents programmers from introducing certain types of bugs related to how memory is used. Since memory safety bugs are often security issues, memory safe languages are more secure than languages that are not memory safe. Memory safe languages include Rust, Go, C#, Java, Swift, Python, and JavaScript. Languages that are not memory safe include C, C++, and assembly. Types of Memory Safety Bugs To begin understanding memory safety bugs, we'll consider the example of an application that maintains to do lists for many users. We'll look at a couple of the most common types of memory safety errors that can occur in programs that are not memory safe.
In this first part about memory safety in Rust we will understand the concept of memory safety and discuss various approaches used by programming languages to achieve it.