У нас вы можете посмотреть бесплатно Choose the Right Option или скачать в максимальном доступном качестве, видео которое было загружено на ютуб. Для загрузки выберите вариант из формы ниже:
Если кнопки скачивания не
загрузились
НАЖМИТЕ ЗДЕСЬ или обновите страницу
Если возникают проблемы со скачиванием видео, пожалуйста напишите в поддержку по адресу внизу
страницы.
Спасибо за использование сервиса ClipSaver.ru
"Reference-to-Option" and "Optional-reference"* are both ways to represent "a reference to a value that may or may not be there" in Rust. So which one should you use in your APIs? Hear me spoil my answer within the first 10 seconds, and then stick around to get real nerdy about a topic you may have never spent 15+ minutes thinking about before. Featuring special guest appearances from memory layout visualizations (feat. niche optimizations), the venerable ToOwned trait, and me saying the word "Data" several hundred times. And yes, I do in fact regret missing the opportunity to make a Sum 41 reference during the memory layout visualization. Option docs - https://doc.rust-lang.org/std/option/... ToOwned docs - https://doc.rust-lang.org/std/borrow/... Niche optimization / "null pointer optimization" (which IS guaranteed for Option-ref-T) - https://doc.rust-lang.org/std/option/... I use the amazing Manim library for animating these videos, and I edit them with Blender and Audacity. https://www.manim.community/ https://www.blender.org/ https://www.audacityteam.org/ *YouTube doesn't allow angle brackets in video descriptions.