P. All rights reserved. © 2024 Bloomberg Finance L.P. All rights reserved. Designing C++ Code Generator Guardrails A collaboration between outreach and development teams & users CppCon 2024 September violated “the principle of least astonishment.” We were offering a modern set of guardrails for Bloomberg’s 20-year-old Code Generator. Others responded before we could. They said they weren’t the least features were used in a feature rich tool; and Made it far easier to continue modernizing the Code Generator. We did it without risk! And we did it with the consensus and participation of dozens of teams

你所不知道的 set 容 器 by 小彭老师（ @archibate ） 课件 & 代码： https://github.com/parallel101/course 上期回顾： https://www.bilibili.com/video/BV1qF411T7sd 课程安排 1. vector 容器初体验 & 迭代器入门 (BV1qF411T7sd) 2. 你所不知道的 set 容器 & ，内存管理与对象生命周期 set 和 vector 的区别 • 都是能存储一连串数据的容器 。 • 区别 1 ： set 会自动给其中的 元素从小到大排序，而 vector 会保持插入时的顺序。 • 区别 2 ： set 会把重复的元素 去除，只保留一个，即去重。 • 区别 3 ： vector 中的元素在内 存中是连续的，可以高效地按 索引随机访问， set 则不行。 • 区别 4 4 ： set 中的元素可以高 效地按值查找，而 vector 则 低效。 set 的排序： string 会按“字典序”来排 • set 会从小到大排序，对 int 来 说就是数值的大小比较。那么对 字符串类型 string 要怎么排序 呢？ • 其实 string 类定义了运算符重 载 < ，他会按字典序比较两个 字符串。所谓字典序就是优先比 较两者第一个字符（按 ASCII 码比较），如果相等则继续比较

. . . . . . . . . . . . . . . . . . . . . . 362 17.11 How to create and share a custom generator with generator packages . . . . . . . . . . . . . . . . . . 365 17.12 How to manage shared libraries . deps_user_info, these have been removed in 2.0. Note: If you don’t need to customize anything in a generator you can specify it in the generators attribute and skip using the generate() method for that: from New properties model Migrating legacy cpp_info attributes to set_property() Migrating from .names, .filenames and .build_modules to set_property() is easy, but there are some details to take into account

. . . . . . . . . . . . . . . . . . . . . . 362 17.11 How to create and share a custom generator with generator packages . . . . . . . . . . . . . . . . . . 365 17.12 How to manage shared libraries . deps_user_info, these have been removed in 2.0. Note: If you don’t need to customize anything in a generator you can specify it in the generators attribute and skip using the generate() method for that: from New properties model Migrating legacy cpp_info attributes to set_property() Migrating from .names, .filenams and .build_modules to set_property() is easy, but there are some details to take into account

. . . . . . . . . . . . . . . . . . . . . . 345 17.11 How to create and share a custom generator with generator packages . . . . . . . . . . . . . . . . . . 348 17.12 How to manage shared libraries . can be done manually. Set up configurations: $ conan config init # Initialize Conan configuration files. If some are already␣ ˓→present, missing files only are # created Set configuration values: $ conan config set

.= $ conan config set log.level=10 $ conan config set log.print_run_commands=False # Make conan less verbose Inspect configurations: $ conan config home #

. . . . . . . . . . . . . . . . . . . . . . 362 17.11 How to create and share a custom generator with generator packages . . . . . . . . . . . . . . . . . . 365 17.12 How to manage shared libraries . deps_user_info, these have been removed in 2.0. Note: If you don’t need to customize anything in a generator you can specify it in the generators attribute and skip using the generate() method for that: from New properties model Migrating legacy cpp_info attributes to set_property() Migrating from .names, .filenams and .build_modules to set_property() is easy, but there are some details to take into account

. . . . . . . . . . . . . . . . . . . . . . 362 17.11 How to create and share a custom generator with generator packages . . . . . . . . . . . . . . . . . . 365 17.12 How to manage shared libraries . deps_user_info, these have been removed in 2.0. Note: If you don’t need to customize anything in a generator you can specify it in the generators attribute and skip using the generate() method for that: from New properties model Migrating legacy cpp_info attributes to set_property() Migrating from .names, .filenams and .build_modules to set_property() is easy, but there are some details to take into account

. . . . . . . . . . . . . . . . . . . . . . 360 17.11 How to create and share a custom generator with generator packages . . . . . . . . . . . . . . . . . . 363 17.12 How to manage shared libraries . deps_user_info, these have been removed in 2.0. Note: If you don’t need to customize anything in a generator you can specify it in the generators attribute and skip using the generate() method for that: from New properties model Migrating legacy cpp_info attributes to set_property() Migrating from .names, .filenams and .build_modules to set_property() is easy, but there are some details to take into account

. . . . . . . . . . . . . . . . . . . . . . 359 17.11 How to create and share a custom generator with generator packages . . . . . . . . . . . . . . . . . . 362 17.12 How to manage shared libraries deps_user_info, these have been removed in 2.0. Note: If you don’t need to customize anything in a generator you can specify it in the generators attribute and skip using the generate() method for that: from New properties model Migrating legacy cpp_info attributes to set_property() Migrating from .names, .filenames and .build_modules to set_property() is easy, but there are some details to take into account

. . . . . . . . . . . . . . . . . . . . . . 370 17.11 How to create and share a custom generator with generator packages . . . . . . . . . . . . . . . . . . 373 17.12 How to manage shared libraries . deps_user_info, these have been removed in 2.0. Note: If you don’t need to customize anything in a generator you can specify it in the generators attribute and skip using the generate() method for that: from New properties model Migrating legacy cpp_info attributes to set_property() Migrating from .names, .filenames and .build_modules to set_property() is easy, but there are some details to take into account