Keep up to date with every new upload!

Join free & follow Channel 9
Share
  • 2 years ago
CppCon 2016: Herb Sutter “Leak-Freedom in C++... By Default.”  | CppCon 2016

CppCon 2016: Herb Sutter “Leak-Freedom in C++... By Default.” | CppCon 2016

Published on Sep 26, 2016http://CppCon.orgPresentation Slides, PDFs, Source Code and other presenter materials are available at: https://github.com/cppcon/cppcon2016Lifetime safety means writing code that, by construction, is guaranteed to eliminate two things: (a) use of null/dangling pointers (including pointerlike things such as references, iterators, views, and ranges), and (b) leaks (including the rare 1% case where we're tempted to admit the possibility of an ownership cycle or need to support lock-free concurrent data structures).Last year, my CppCon 2015 talk "Writing Good C++14... By Default" focused on (a), null/dangling, because it's the more difficult and usually more serious problem. I gave an overview of a new approach of using static analysis rules to eliminate use of null and dangling in C++. That work continues and we're in the process of writing down the formal rules for the approach that I showed last year.This year, the focus will be on (b)

Comments