\chapter{Paths}
\hypertarget{md_home_2simon_2workspace_2post-scarcity_2docs_2_paths}{}\label{md_home_2simon_2workspace_2post-scarcity_2docs_2_paths}\index{Paths@{Paths}}
\label{md_home_2simon_2workspace_2post-scarcity_2docs_2_paths_autotoc_md102}%
\Hypertarget{md_home_2simon_2workspace_2post-scarcity_2docs_2_paths_autotoc_md102}%
 {\itshape See also \href{How do we notate paths?.html}{\texttt{ How do we notate paths?}}, which in part supercedes this.}

A path is essentially a list of keywords.

However, the path {\ttfamily (\+:aardvark \+:beluga \+:coeleocanth \+:dodo)} may be denoted {\ttfamily \+:aardvark\+:beluga\+:coeleocanth\+:dodo} and will be expanded into a list by the reader. If the value of {\ttfamily \+:ardvark} in the current environment is a map, and the value of {\ttfamily \+:beluga} in that map is a map, and the value of {\ttfamily \+:coeleocanth} in that map is a map, then the value of the path {\ttfamily \+:aardvark\+:beluga\+:coeleocanth\+:dodo} is whatever the value of {\ttfamily \+:dodo} is in the map indicated by {\ttfamily \+:aardvark\+:beluga\+:coeleocanth}; however if the path cannot be fully satisfied the value is {\ttfamily nil}.

The notation {\ttfamily \+::aardvark\+:beluga\+:coeleocanth\+:dodo} is expanded by the reader into {\ttfamily ((oblist) \+:aardvark \+:beluga \+:coeleocanth \+:dodo)}, or, in other words, is a path from the root namespace. 