inside module NameOfModule ... end, and have the following features: 1. Modules are separate namespaces, each introducing a new global scope. This is useful, because it allows the same name to be used contain submodules, nesting the same syntax module ... end. They can be used to introduce separate namespaces, which can be helpful for organizing complex codebases. Note that each module introduces its own argument type, not only this, using the most-specific-declaration rule). Julia ⇔ C/C++: Namespaces • C/C++ namespaces correspond roughly to Julia modules. • There are no private globals or fields in Julia

inside module NameOfModule ... end, and have the following features: 1. Modules are separate namespaces, each introducing a new global scope. This is useful, because it allows the same name to be used contain submodules, nesting the same syntax module ... end. They can be used to introduce separate namespaces, which can be helpful for organizing complex codebases. Note that each module introduces its own argument type, not only this, using the most-specific-declaration rule). Julia ⇔ C/C++: Namespaces • C/C++ namespaces correspond roughly to Julia modules. • There are no private globals or fields in Julia

inside module NameOfModule ... end, and have the following features: 1. Modules are separate namespaces, each introducing a new global scope. This is useful, because it allows the same name to be used contain submodules, nesting the same syntax module ... end. They can be used to introduce separate namespaces, which can be helpful for organizing complex codebases. Note that each module introduces its own argument type, not only this, using the most-specific-declaration rule). Julia ⇔ C/C++: Namespaces • C/C++ namespaces correspond roughly to Julia modules. • There are no private globals or fields in Julia

inside module NameOfModule ... end, and have the following features: 1. Modules are separate namespaces, each introducing a new global scope. This is useful, because it allows the same name to be used contain submodules, nesting the same syntax module ... end. They can be used to introduce separate namespaces, which can be helpful for organizing complex codebases. Note that each module introduces its own argument type, not only this, using the most-specific-declaration rule). Julia ⇔ C/C++: Namespaces • C/C++ namespaces correspond roughly to Julia modules. • There are no private globals or fields in Julia

inside module NameOfModule ... end, and have the following features: 1. Modules are separate namespaces, each introducing a new global scope. This is useful, because it allows the same name to be used contain submodules, nesting the same syntax module ... end. They can be used to introduce separate namespaces, which can be helpful for organizing complex codebases. Note that each module introduces its own type, not only this, using the most-specific-declaration rule). Julia ⇔ C/C++: Namespaces • C/C++ namespaces correspond roughly to Julia modules. • There are no private globals or fields in Julia

inside module NameOfModule ... end, and have the following features: 1. Modules are separate namespaces, each introducing a new global scope. This is useful, because it allows the same name to be used contain submodules, nesting the same syntax module ... end. They can be used to introduce separate namespaces, which can be helpful for organizing complex codebases. Note that each module introduces its own type, not only this, using the most-specific-declaration rule). Julia ⇔ C/C++: Namespaces • C/C++ namespaces correspond roughly to Julia modules. • There are no private globals or fields in Julia

inside module NameOfModule ... end, and have the following features: 1. Modules are separate namespaces, each introducing a new global scope. This is useful, because it allows the same name to be used contain submodules, nesting the same syntax module ... end. They can be used to introduce separate namespaces, which can be helpful for organizing complex codebases. Note that each module introduces its own type, not only this, using the most-specific-declaration rule). Julia ⇔ C/C++: Namespaces • C/C++ namespaces correspond roughly to Julia modules. • There are no private globals or fields in Julia

inside module NameOfModule ... end, and have the following features: 1. Modules are separate namespaces, each introducing a new global scope. This is useful, because it allows the same name to be used contain submodules, nesting the same syntax module ... end. They can be used to introduce separate namespaces, which can be helpful for organizing complex codebases. Note that each module introduces its own type, not only this, using the most-specific-declaration rule). Julia ⇔ C/C++: Namespaces • C/C++ namespaces correspond roughly to Julia modules. • There are no private globals or fields in Julia

inside module NameOfModule ... end, and have the following features: 1. Modules are separate namespaces, each introducing a new global scope. This is useful, because it allows the same name to be used contain submodules, nesting the same syntax module ... end. They can be used to introduce separate namespaces, which can be helpful for organizing complex codebases. Note that each module introduces its own type, not only this, using the most-specific-declaration rule). Julia ⇔ C/C++: Namespaces • C/C++ namespaces correspond roughly to Julia modules. • There are no private globals or fields in Julia

inside module NameOfModule ... end, and have the following features: 1. Modules are separate namespaces, each introducing a new global scope. This is useful, because it allows the same name to be used contain submodules, nesting the same syntax module ... end. They can be used to introduce separate namespaces, which can be helpful for organizing complex codebases. Note that each module introduces its own type, not only this, using the most-specific-declaration rule). Julia ⇔ C/C++: Namespaces • C/C++ namespaces correspond roughly to Julia modules. • There are no private globals or fields in Julia