#include // [...]10/50 Hello Modules! — File: module.cpp export module my_module; export char const* my_function () { return "Hello Modules!"; } — File: main.cpp #include }11/50 Exporting things // functions export int getNumber (); // types export class SomeType; // templates export template T combine(T n1 , T n2); export template class MyTemplatedType Exporting things export namespace a { void is_exported (); } namespace a { void is_not_exported (); } namespace a { void will_be_exported_in_b (); } export namespace b { export using a:: will_be_exported_in_b

object file 6 . 2 discarded discarded some header.hsource.cpp translation unit object file export module library; library interface unit module library; library implementation library implementation implementation object file import library; program library interface object file 7 . 1 export ...; export ...; BMI BMI Barrier→║ Architected→→ modularized library some allinterface.cpp declarations 4 5 6 7 8 9 module; #include export module my.first_module; export import other.module; #include "mod.h" constexpr int beast = 666; export std::vector frob(S); 1 2 3 4 5 6 7 8 9

'conancenter'... Downloading conanmanifest.txt Downloading conanfile.py Downloading conan_export.tgz Decompressing conan_export.tgz zlib/1.2.11: Downloaded recipe revision f1fadf0d3b196dc0332750354ad8ab7b Graph the recipe is never called and could be removed. 3. We call conan export-pkg to package the built artifacts. $ cd ../.. $ conan export-pkg . -s build_type=Release ... hello/0.1: Calling package() hello/0 call conan export-pkg command, later we can list the binaries so we can check we have one package for each precompiled library: $ conan export-pkg . -s os="Linux" -s arch="x86_64" $ conan export-pkg . -s

'conancenter'... Downloading conanmanifest.txt Downloading conanfile.py Downloading conan_export.tgz Decompressing conan_export.tgz zlib/1.2.11: Downloaded recipe revision f1fadf0d3b196dc0332750354ad8ab7b Graph the recipe is never called and could be removed. 3. We call conan export-pkg to package the built artifacts. $ cd ../.. $ conan export-pkg . -s build_type=Release ... hello/0.1: Calling package() hello/0 call conan export-pkg command, later we can list the binaries so we can check we have one package for each precompiled library: $ conan export-pkg . -s os="Linux" -s arch="x86_64" $ conan export-pkg . -s

'conancenter'... Downloading conanmanifest.txt Downloading conanfile.py Downloading conan_export.tgz Decompressing conan_export.tgz zlib/1.2.11: Downloaded recipe revision f1fadf0d3b196dc0332750354ad8ab7b Graph the recipe is never called and could be removed. 3. We call conan export-pkg to package the built artifacts. $ cd ../.. $ conan export-pkg . -s build_type=Release ... hello/0.1: Calling package() hello/0 call conan export-pkg command, later we can list the binaries so we can check we have one package for each precompiled library: $ conan export-pkg . -s os="Linux" -s arch="x86_64" $ conan export-pkg . -s

'conancenter'... Downloading conanmanifest.txt Downloading conanfile.py Downloading conan_export.tgz Decompressing conan_export.tgz zlib/1.2.11: Downloaded recipe revision f1fadf0d3b196dc0332750354ad8ab7b Graph the recipe is never called and could be removed. 3. We call conan export-pkg to package the built artifacts. $ cd ../.. $ conan export-pkg . -s build_type=Release ... hello/0.1: Calling package() hello/0 call conan export-pkg command, later we can list the binaries so we can check we have one package for each precompiled library: $ conan export-pkg . -s os="Linux" -s arch="x86_64" $ conan export-pkg . -s

'conancenter'... Downloading conanmanifest.txt Downloading conanfile.py Downloading conan_export.tgz Decompressing conan_export.tgz zlib/1.2.11: Downloaded recipe revision f1fadf0d3b196dc0332750354ad8ab7b Graph the recipe is never called and could be removed. 3. We call conan export-pkg to package the built artifacts. $ cd ../.. $ conan export-pkg . -s build_type=Release ... hello/0.1: Calling package() hello/0 call conan export-pkg command, later we can list the binaries so we can check we have one package for each precompiled library: $ conan export-pkg . -s os="Linux" -s arch="x86_64" $ conan export-pkg . -s

your .condarc file: notify_outdated_conda: false Managing environments With conda, you can create, export, list, remove, and update environments that have different versions of Python and/or packages installed --file argument. • Pip accepts a list of Python packages with -r or --requirements. • Conda env will export or create environments based on a file with conda and pip requirements. Setting environment variables Environment variables set using conda env config vars will be retained in the output of conda env export. Further, you can declare environment variables in the environment.yml file as shown here: 4.1.

your .condarc file: notify_outdated_conda: false Managing environments With conda, you can create, export, list, remove, and update environments that have different versions of Python and/or packages installed --file argument. • Pip accepts a list of Python packages with -r or --requirements. • Conda env will export or create environments based on a file with conda and pip requirements. Setting environment variables Environment variables set using conda env config vars will be retained in the output of conda env export. Further, you can declare environment variables in the environment.yml file as shown here: 4.1.

your .condarc file: notify_outdated_conda: false Managing environments With conda, you can create, export, list, remove, and update environments that have different versions of Python and/or packages installed --file argument. • Pip accepts a list of Python packages with -r or --requirements. • Conda env will export or create environments based on a file with conda and pip requirements. Setting environment variables Environment variables set using conda env config vars will be retained in the output of conda env export. Further, you can declare environment variables in the environment.yml file as shown here: 4.1.