nothing

The singleton instance of typeNothing, used by convention when there is no value to return (as in a Cvoid function) or when a variable or field holds no value.

A return value ofnothing is not displayed by the REPL and similar interactive environments.

See also:isnothing,something,missing.

PROGRAM_FILE

A string containing the script name passed to Julia from the command line. Note that the script name remains unchanged from within included files. Alternatively see@__FILE__.

ARGS

An array of the command line arguments passed to Julia, as strings.

C_NULL

The C null pointer constant, sometimes used when calling external code.

VERSION

AVersionNumber object describing which version of Julia is in use. See alsoVersion Number Literals.

DEPOT_PATH

A stack of "depot" locations where the package manager, as well as Julia's code loading mechanisms, look for package registries, installed packages, named environments, repo clones, cached compiled package images, and configuration files. By default it includes:

1. ~/.julia where~ is the user home as appropriate on the system;
2. an architecture-specific shared system directory, e.g./usr/local/share/julia;
3. an architecture-independent shared system directory, e.g./usr/share/julia.

SoDEPOT_PATH might be:

[joinpath(homedir(), ".julia"), "/usr/local/share/julia", "/usr/share/julia"]

The first entry is the "user depot" and should be writable by and owned by the current user. The user depot is where: registries are cloned, new package versions are installed, named environments are created and updated, package repos are cloned, newly compiled package image files are saved, log files are written, development packages are checked out by default, and global configuration data is saved. Later entries in the depot path are treated as read-only and are appropriate for registries, packages, etc. installed and managed by system administrators.

DEPOT_PATH is populated based on theJULIA_DEPOT_PATH environment variable if set.

DEPOT_PATH contents

Each entry inDEPOT_PATH is a path to a directory which contains subdirectories used by Julia for various purposes. Here is an overview of some of the subdirectories that may exist in a depot:

• artifacts: Contains content that packages use for which Pkg manages the installation of.
• clones: Contains full clones of package repos. Maintained byPkg.jl and used as a cache.
• config: Contains julia-level configuration such as astartup.jl.
• compiled: Contains precompiled*.ji files for packages. Maintained by Julia.
• dev: Default directory forPkg.develop. Maintained byPkg.jl and the user.
• environments: Default package environments. For instance the global environment for a specific julia version. Maintained byPkg.jl.
• logs: Contains logs ofPkg andREPL operations. Maintained byPkg.jl and Julia.
• packages: Contains packages, some of which were explicitly installed and some which are implicit dependencies. Maintained byPkg.jl.
• registries: Contains package registries. By default onlyGeneral. Maintained byPkg.jl.
• scratchspaces: Contains content that a package itself installs via theScratch.jl package.Pkg.gc() will delete content that is known to be unused.

See alsoJULIA_DEPOT_PATH, andCode Loading.

LOAD_PATH

An array of paths forusing andimport statements to consider as project environments or package directories when loading code. It is populated based on theJULIA_LOAD_PATH environment variable if set; otherwise it defaults to["@", "@v#.#", "@stdlib"]. Entries starting with@ have special meanings:

• @ refers to the "current active environment", the initial value of which is initially determined by theJULIA_PROJECT environment variable or the--project command-line option.

• @stdlib expands to the absolute path of the current Julia installation's standard library directory.

• @name refers to a named environment, which are stored in depots (seeJULIA_DEPOT_PATH) under theenvironments subdirectory. The user's named environments are stored in~/.julia/environments so@name would refer to the environment in~/.julia/environments/name if it exists and contains aProject.toml file. Ifname contains# characters, then they are replaced with the major, minor and patch components of the Julia version number. For example, if you are running Julia 1.2 then@v#.# expands to@v1.2 and will look for an environment by that name, typically at~/.julia/environments/v1.2.

The fully expanded value ofLOAD_PATH that is searched for projects and packages can be seen by calling theBase.load_path() function.

See alsoJULIA_LOAD_PATH,JULIA_PROJECT,JULIA_DEPOT_PATH, andCode Loading.

Sys.BINDIR::String

A string containing the full path to the directory containing thejulia executable.

Sys.CPU_THREADS::Int

The number of logical CPU cores available in the system, i.e. the number of threads that the CPU can run concurrently. Note that this is not necessarily the number of CPU cores, for example, in the presence ofhyper-threading.

See Hwloc.jl or CpuId.jl for extended information, including number of physical cores.

Sys.WORD_SIZE::Int

Standard word size on the current machine, in bits.

Sys.KERNEL::Symbol

A symbol representing the name of the operating system, as returned byuname of the build configuration.

Sys.ARCH::Symbol

A symbol representing the architecture of the build configuration.

Sys.MACHINE::String

A string containing the build triple.