# Top 5 improvements to Debugging Go Code in VS Code in the last year Ramya Rao Software Engineer, Microsoft Maintainer of the Go plugin to VS Code ## Add/remove breakpoints when in the middle of debugging

## +21 ## Code Analysis++ ## ANASTASIA KAZAKOVA ## 20 21 October 24-29 • Anastasia Kazakova, @anastasiak2512 C++ Dev: Embedded, Networking C++ Tools PMM and .NET Tools Marketing Lead, JetBrains - UG: https://www.meetup.com/St-Petersburg-CPP-User-Group/ C++ Russia: https://cppconf.ru/en/ ## Why Code Analysis? ## Software Quality While preparing for my workshop at #CppOnSea, I want to ask you: reply about software quality. Readability Repeatable tests SW helps solving Maintainability Expressive code less UB problems Simplicity tools Robustness The Last Spike Work as intended fuzzer Orthogonality

+23 ## Better Code: Contracts ## SEAN PARENT & DAVE ABRAHAMS ## 20 23 October 01 - 06  ## Better Code: Contracts Dave Co-creator Documentation > Code  Local reasoning is the idea that the reader can make sense of the code directly in front of them them, without going on a journey discovering how the code works. ## —Nathan Gitter (https://medium.com/@nathangitter/local-reasoning-in-swift-6782e459d) ## Local reasoning | The tower of abstraction

## Designing an ultra low-overhead multithreading runtime for Nim Mamy Ratsimbazafy mamy@numforge.co ## Hello! ## I am Mamy Ratsimbazafy During the day blockchain/Ethereum 2 developer (in Nim) During detail if non-lazy splitting: - “Grain size” Why: - Easier to port decades of OpenMP scientific code Synchronization: Shared memory for data Barriers (if not built on top of task parallelism) Dataflow Public deques are constrained by push/pop/steal/steal-half - Steal requests are implicit and have very low-overhead - Thieves can check if a victim deque is empty - They don’t work in a distributed setting

### Interesting Upcoming Features from Low Latency, Parallelism and Concurrency From Kona 2023, Tokyo 2024, and St. Louis 2024 PAUL E. MCKENNEY, MAGED MICHAEL & MICHAEL WONG 20 24 September 15 proper usage of atomic min/max, you can leverage their power to build robust and reliable concurrent code. ## Atomic Floating-Point Min/Max in C++ (P3008) Atomic min/max operations are crucial for concurrent Causes Enables Results in CAS Performance Degradation High Performance Lower Performance ## Code Examples #include #include $\#includeint\; main()\; \{\; std::atomic$

Leveraging C++20/23 Features for Low Level Interactions © ## Overview In a baremetal environment, we’re going to demonstrate effective use of C++ How did we end up with C language HW interactions? What cleaner, safer, and more testable? Why is C so prolific? It's the kernel, silly! 30 years ago, all low level interaction was done with C Organizations are very comfortable with C in embedded applications dangerous C-like code. Why not rewrite all the C code? There’s LOTS of code out there! $ ^{1} $ 1. See also Stroustrup (2023), in references Why not rewrite all the C code? There’s LOTS of code out there

## +24 ## Work Contracts Rethinking Task Based Concurrency and Parallelism for Low Latency C++ MICHAEL A MANISCALCO ### “We cannot solve our problems with the same thinking we used when we created them Michael A Maniscalco ○ Software Architect and Principal Developer at Lime Trading ○ We develop low latency market data and trading software for use in HFT ## • Personal github.com/buildingcpp Work Contract (Logic) Data Data Data Execute Logic(Data) Execute Logic(Data) ## Resources: Source Code: github.com/buildingcpp/work_contract ![Image](/uploads/documents/1/0/e/c/10ec85450d246c7c9a1e6a288ea9d54e/p14_1

## GARMIN $ ^{®} $ ## Changing Legacy Code with Confidence: ## Practical Advice for Maintaining and Migrating Working Code ## Part 0: Legacy Code ## Legacy code has value • It works $ ^{*} $ It may making the company money • One person's bug is another's critical feature ## The Legacy of Code • Best practices and languages change • Developers cycle through projects • Features added/removed/re-added • Supporting tools change ## Goals of this talk • Preserve working code • Introduce testing • Gradual improvement • Make code self documenting • Instill confidence in changes • Develop for maintenance

## CODE GENERATION FOR VULKAN INITIALIZATION ## LEARNING VULKAN • So... • I’ve decided to learn Vulkan. • Did I learn it? • Not yet. ## WHAT DID I LEARN? ## THIS: ### Copyright © 2019-2019, NVIDIA platforms • #define platform selection • All extensions ## DEPENDENCIES ## WHAT DID I DO? • Simple code generation ■ XSLT translation to header file • Enumerate all the things ■ Platforms, extensions

## +23 ## Better Code: Exploring Validity ## DAVID SANKEL ## 20 23 October 01 - 06  ## Better Code Exploring Validity Events • Training Videos (STLab Better Code Series!) ■ Blog Posts  ## Better Code Functional Design David Sankel | Principal jpg)  ## Better Code: Reliable Types Nick DeMarco | Senior Computer Scientist Software Technology Lab #### developer