Из-за периодической блокировки нашего сайта РКН сервисами, просим воспользоваться резервным адресом:
Загрузить через dTub.ru Загрузить через ClipSaver.ruУ нас вы можете посмотреть бесплатно Cppcon 2018 andrei alexandrescu expect the expected или скачать в максимальном доступном качестве, которое было загружено на ютуб. Для скачивания выберите вариант из формы ниже:
Роботам не доступно скачивание файлов. Если вы считаете что это ошибочное сообщение - попробуйте зайти на сайт через браузер google chrome или mozilla firefox. Если сообщение не исчезает - напишите о проблеме в обратную связь. Спасибо.
Если кнопки скачивания не
загрузились
НАЖМИТЕ ЗДЕСЬ или обновите страницу
Если возникают проблемы со скачиванием, пожалуйста напишите в поддержку по адресу внизу
страницы.
Спасибо за использование сервиса savevideohd.ru
Download 1M+ code from https://codegive.com/bf8ba15 andrei alexandrescu's "expect the expected" at cppcon 2018: a deep dive andrei alexandrescu's "expect the expected" talk at cppcon 2018 explores a powerful technique for improving code reliability and performance by leveraging compile-time guarantees about the expected state of variables and data structures. he argues that by explicitly encoding these expectations into your code, you can: *detect errors earlier:* fail at compile time or during testing, rather than encountering unexpected behavior in production. *improve performance:* allow the compiler to optimize code based on the guaranteed properties of your data. *enhance code readability:* make the intent of the code clearer to other developers (and your future self). this tutorial will break down the key concepts from alexandrescu's talk, providing code examples and explanations to help you understand and apply these techniques in your c++ projects. *i. the problem: implicit expectations and hidden assumptions* a significant portion of bugs arise from unexpected states in variables or data structures. these often stem from implicit expectations – assumptions we make about the valid range, properties, or lifecycle of data. consider this simple example: here, we expect `value` to be non-negative. however, this expectation is only encoded within the function's logic. if a negative value slips through (perhaps from another part of the program), the `process_value` function has to handle it, usually through error checking and a potentially less-than-ideal fallback. *the issues:* *runtime checks:* error handling happens at runtime, potentially causing a performance hit. *delayed detection:* the error might not be discovered until the code is running in production. *hidden intent:* the expectation is only apparent by reading the code, not explicit in the type system. *fallback mechanisms:* the code needs to define what to do when the expectation is ... #CppCon #AndreiAlexandrescu #ExpectTheExpected Cppcon 2018 Andrei Alexandrescu C++ programming software development modern C++ generic programming design patterns performance optimization code quality software engineering template metaprogramming concurrency algorithms best practices