0x27: A rehearsal for safety

I'm excited to share that we have a special treat for our upcoming meetup: a brand-new talk by Timur Doumler! This will be a premiere event, so don't miss your chance to be among the first to hear it. Please note that no video will be released, so this is truly a unique opportunity. In addition to Timur's talk, we'll have some lightning talks to kick off the evening. These talks may be recorded and shared later.

Thank you NetInsight, for generously hosting our event and being a SwedenCpp Pro Sponsor!

The program:

• 17:45 Door open
• 18:00 - 18:45 Intro and lightning talks
• 18:45 - 19:45 Mingle time
• 19:45 - 20:45 Timur Doumler: C++ and Safety

The program in detail:

• Lightning talks
  Björn Fahller: A quick guide through Non Type Template Parameters
  Non type template parameters have been a part of C++ since before it was standardized, but it saw a small, but important, facelift in C++17 and a major improvement in C++23. I will give you examples of the evolution and how using the improvements helps your code become more expressive.
  Arvid Norberg: Efficient parsing
  A space-efficient and cache-friendly internal data structure to parse JSON-like objects into, compared with naive structures.
• Mingle time
  Our usual meet, greet and chat part with pizza and drinks.
• Timur Doumler: C++ and Safety
  Organisations such as the National Security Angency (NSA) and the National Institute of Standards and Techology (NIST) are currently urging developers to move away from programming languages that are not memory safe. C++ is arguably not a "safe" programming language in its current form. Why is that? And should we do anything about it? If yes, what, and how? Have we arrived at a crossroads for the future evolution of C++? What does "safety" even mean, and how is it different from "security" and "correctness"?
  In this talk, we attempt to give useful definitions for these terms. For safety in particular, we can distinguish between functional safety and language safety, and identify different aspects of language safety (of which memory safety is one). We discuss how and why C++ is considered "unsafe" and what consequences follow from that for different domains and use cases. We look at how other programming languages, such as Java, Rust, and Val avoid such safety issues, what tradeoffs are involved in these strategies, and why we can't easily adopt any of them for C++. We consider the tooling available today to mitigate safety issues in C++, such as sanitisers and static analysers, and their limitations. Finally, we look at the future evolution of C++ and discuss the current work on C++ Contracts and other recent proposals targeted at making C++ more safe.

Väl mött!