u/mttdin r/ProgrammingLanguages ā¢ Recommends
Mojoš„: a deep dive on ownership with Chris Lattner
0:00 / 0:00
Mojoš„: a deep dive on ownership with Chris Lattner
Modular
15K subscribers ā¢ 3 videos on Hallway
- Recommended by 2 people: 1 on Lobsters and 1 in engineering communities.
- Presented by Chris Lattner, CEO of Modular
- Made by the vendor. The company whose product it covers made or sponsored it.
Intermediate. Assumes working knowledge.
51K views2 years ago2 recommendations
Programming languagesSystems programmingLanguage design and type systemsMemory managementCompilers and interpreters
Chris Lattner explains the ownership model, value categories, and compiler mechanics behind Mojo.
Learn everything you need to know about ownership in Mojo, a deep dive with Modular CEO Chris Lattner If you have any questions make sure to join our friendly Discord community: modul.ar/discord If you're ready to get started with Mojo, check out the programming manual and installation guide: modul.ar/mojo-get-started Mojoš„: a deep dive on ownership with Chris Lattner Introduction Define Terms Garbage Collectors Copies Goal of ownership model Learning from Rust How the compiler works Type Checker Context Insensitive Type Checker No traditional AST Ownership RValue: an owned value LValues: assignable and mutable BValues: Borrowed Values Ownership conversions BValue Conversions RValue Conversions LValue Conversions Examples of RValues Memory and SSA Types Ownership Transfer with ^ std::move from C++ Marking variables as uninitialized after transfer with ^ Data flow checker with argument conventions Destructor Insertion ASAP Destruction Avoiding allocations optimization Copy to move optimizations @value decorator Where does destructor run on borrowed argument Copy to move optimization clarification #programminglanguages #programming #python #ml Is liveness representable in debug info? How ASAP destruction works with loops Being simple and optimal Allowing more advanced use cases and reducing copies Field sensitive and composes with member variables Dangling pointers What safe references will fix