A new approach to meta programming Author: Andreas Rumpf A new approach to metaprogramming Copyright © 2013 Andreas Rumpf Talk structure 1.What is Nimrod? 2.Implementation aspects 3."Hello World"

Monadic Operations in Modern C++: A Practical Approach2About me ● Vitaly Fanaskov ● Senior software engineer at reMarkable ● 10+ years of C++ experience ● GIS, VFX, frameworks, and libraries ● Ph Monadic interface ● Separation of functional and non-functional code 42Small steps 43General approach (assume you have OO-style code-base) 44 ● Start with the implementation of the methods ● Partially

Outline ● Introduction ● Overview of ROS 2 ● ROS 2 Conventional Approach ● Introduction to Functional Programming Principles ● Refactoring using Functional Programming Principles ● ConclusionIntroductionAbout map Clip from https://www.youtube.com/watch?v=VTeY-l-Xh6cROS 2 Conventional ApproachConventional Approach class PathGenerator : public rclcpp::Node { public: explicit PathGenerator( rclcpp::NodeOptions the ROS 2 documentation ● This implementation follows an object oriented approachConventional Approach class PathGenerator : public rclcpp::Node { public: explicit PathGenerator( rclcpp::NodeOptions

in practice • We just made it work, indeed 73A first attempt… • There are even upsides to this approach • Teachable (many are familiar with inheritance and virtual functions) • Structural commonality write for(auto && p : attackers) p->hit(...); 74A first attempt… • There are even upsides to this approach • Teachable (many are familiar with inheritance and virtual functions) • Structural commonality Character::suffer(armor? static_cast(damage * armor->protection()): damage); } }; The non-intrusive approach here is clear from source code: an object is « Damageable » if it can suffer() an int value (we

Acquisition Framework to benefit from Agile development best practices. To succeed with an Agile approach, program managers need to work with stakeholders representing the requirements, systems engineering promote delivery of information technology (IT) capabilities in small, frequent releases – the approach that characterizes Agile development. Although broad adoption of Agile methods across the commercial Implementing an Agile Approach.............................................................................................................. 6 3 Deciding to Adopt an Agile Approach ...................

to enable an outstanding developer experience. GitOps is the best way to enable this platform approach. These two sentences are a concise summary of the key ideas in this paper. In the last few years code. The way to foster an outstanding developer experience is to leverage the internal platform approach. An internal platform helps to get resources to developers on-demand and in a secure way. FAANG development velocity.” James Governor, — Source Redmonk.com Executive summary Adopting the platform approach alone is not enough. Organizations need to think strategically about how they would go about building

.......... 82 7.3.1. High-level approach .................................................................................................. 82 7.3.2. Low-level approach ............................... ....................................... 87 7.5.2. BeanNameAutoProxyCreator, another declarative approach ........................................................................................... 90 7 of the BeanFactory and adds on to it in terms of features, while also allowing a more declarative approach to use of some functionality, which is generally desirable. The main usage scenario when you might

.......... 89 8.3.1. High-level approach .................................................................................................. 89 8.3.2. Low-level approach ............................... ....................................... 94 8.5.2. BeanNameAutoProxyCreator, another declarative approach ........................................................................................... 97 8 of the BeanFactory and adds on to it in terms of features, while also allowing a more declarative approach to use of some functionality, which is generally desirable. The main usage scenario when you might

........ 100 8.3.1. High-level approach .................................................................................................. 100 8.3.2. Low-level approach ............................... ...................................... 105 8.5.2. BeanNameAutoProxyCreator, another declarative approach ........................................................................................... 108 of the BeanFactory and adds on to it in terms of features, while also allowing a more declarative approach to use of some functionality, which is generally desirable. The main usage scenario when you might

.......... 81 7.3.1. High-level approach .................................................................................................. 81 7.3.2. Low-level approach ............................... ....................................... 86 7.5.2. BeanNameAutoProxyCreator, another declarative approach ........................................................................................... 89 7 of the BeanFactory and adds on to it in terms of features, while also allowing a more declarative approach to use of some functionality, which is generally desirable. The main usage scenario when you might