mirre-mt/ masters-thesis
Archived
1
0
Fork 0
Code Releases 1 Activity

fix a couple of quotations

This commit is contained in:
surtur 2023-08-23 11:09:23 +02:00
parent 958f7340e6
commit 8ef19be790
Signed by: wanderer
SSH Key Fingerprint: SHA256:MdCZyJ2sHLltrLBp0xQO0O1qTW9BT/xl5nXkDvhlMCI
1 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
tex/part-theoretical.tex
View File

@ -443,9 +443,9 @@ INI, JSON, YAML, to name some of the popular ones (as of today).
Dhall stood out as a language that was designed with both security and the
needs of dynamic configuration scenarios in mind, borrowing a concept or two
from Nix~\cite{nixoslearn}~\cite{nixlang} (which in turn sources more than a
few of its concepts from Haskell), and in its apparent core being very similar
to JSON, which adds to a familiar feel. In fact, in Dhall's authors' own words
from Nix (which in turn sources more than a few of its concepts from Haskell),
and in its apparent core being very similar to JSON, which adds to a familiar
feel~\cite{nixlang},~\cite{nixoslearn}. In fact, in Dhall's authors' own words
it is: ``a programmable configuration language that you can think of as: JSON +
functions + types + imports''~\cite{dhalllang}.
@ -481,14 +481,14 @@ mount persistent volumes to pertinent locations.
To describe the way Dhall works when performing an evaluation, it resolves
every expression down to a combination of its most basic types (eliminating all
abstraction and indirection) in the process called
\textbf{normalisation}~\cite{dhallnorm} and then saves this result in the
host's cache. The \texttt{dhall-haskell} binary attempts to resolve the
variable \texttt{\$\{XDG\_CACHE\_HOME\}} (have a look at \emph{XDG Base
Directory Spec}~\cite{xdgbasedirspec} for details) to decide \emph{where} the
results of the normalisation will be written for repeated use. Do note that
this behaviour has been observed on a GNU/Linux host and the author has not
verified this behaviour on another platforms, such as FreeBSD.
abstraction and indirection) in the process called \textbf{normalisation} and
then saves this result in the host's cache~\cite{dhallnorm}. The
\texttt{dhall-haskell} binary attempts to resolve the variable
\texttt{\$\{XDG\_CACHE\_HOME\}} (have a look at \emph{XDG Base Directory Spec}
for details) to decide \emph{where} the results of the normalisation will be
written for repeated use~\cite{xdgbasedirspec}. Do note that this behaviour has
been observed on a GNU/Linux host and the author has not verified this
behaviour on another platforms, such as FreeBSD.
If normalisation is performed inside an ephemeral container (as opposed to, for
instance, an interactive desktop session), the results effectively get lost on