C++ in the Cloud One NIF at a Time with Elixir Sakshi Verma | Senior Software Engineerhttps://www.linkedin.com/in/sakverma Functional, concurrent language built for scalability. Ideal for managing managing large-scale cloud applications. Built on the Erlang VM, ensuring resilience and fault tolerance. What is Elixir?https://www.linkedin.com/in/sakverma The Smooth Sailing…https://www.linkedin

next = Clone(curr); while (ReproduceProblem(next) && ResourcesAvailableToRepair(next)) { auto insight = async(launch::async, &MyJob::UnderstandProblem, this, next); auto location = async(launch::async this, next); auto category = async(launch::async, &MyJob::ClassifyProblem, this, next); WaitFor(insight, location, category); next = AttemptToRepair(next); } return (ProblemFixed()) ? Deliver(next) next = Clone(curr); while (ReproduceProblem(next) && ResourcesAvailableToRepair(next)) { auto insight = async(launch::async, &MyJob::UnderstandProblem, this, next); auto location = async(launch::async

cv-qualifiers starts with understanding the structure of declarations… 29 The Structure of Declarations Insight: Every object and function declaration has two main parts:  a sequence of one or more declaration []mean “array”  ()mean “function” 31 Type vs. Non-type Specifiers Insight: Type specifiers modify other type specifiers. Insight: Non-type specifiers apply directly to the declarator-id. static unsigned (and Doesn't Mean) Copyright © 2024 by Ben Saks and Dan Saks 0-15 volatile is a Type-Specifier Insight: The order of the declaration specifiers doesn’t matter to the compiler.  These two declarations

} Let the HW do the right thing • Microcoded subroutine • Aware of platform specifics • Has insight into internal machine stateExample – memcpy: ERMS 92 0000000000001260 <_Z11memcpy_ermsPvPKvm>: } Let the HW do the right thing • Microcoded subroutine • Aware of platform specifics • Has insight into internal machine state Will this universally be the best option? Only representative performance

ftsd::get<"item">(row) << " "; std::cout << get<"discount_code">(row).value_or("") << "\n"; }Key Design Insight u For types with SQL, you only need to worry about input and out u If you can just annotate the

Software Solutions6 Where did CMake come from? • Kitware was the lead engineering team for the Insight Segmentation and Registration Toolkit (ITK) http://www.itk.org – tasked with making it build on

unpractical to do for a real application ○ It would lack the call site information which would limit the insight users can get about where and why allocations happen, making the debugging and reasoning harder

Copyright © 2020-2021 by W alter E. Brown. All rights reserved. 20 An important insight • Given two values a and b, in that order: � Unless we find a reason to the contrary, … � min should

of caution I will at times lead you astray. This is intentional and will hopefully deepen your insight. We will be largely ignoring multithreading for this talk. This is not a best-practice talk.16/55

Copyright © 2022-2024 by Walter E. Brown. All rights reserved. I greatly appreciated the issue’s insight … • … and the resulbng improvements in the specificabon of my nonesuch type. • In addibon, I now