glossary: add join points paper reference

Author: doyougnu

bib/book.bib

@@ -322,3 +322,19 @@ @techreport{BagwellHAMT
   institution={Ecole polytechnique fédérale de Lausanne},
   year={2001}
 }
+
+@inproceedings{historyOfHaskell,
+author = {Hudak, Paul and Hughes, John and Peyton Jones, Simon and Wadler, Philip},
+title = {A History of Haskell: Being Lazy with Class},
+year = {2007},
+isbn = {9781595937667},
+publisher = {Association for Computing Machinery},
+address = {New York, NY, USA},
+url = {https://doi.org/10.1145/1238844.1238856},
+doi = {10.1145/1238844.1238856},
+abstract = {This paper describes the history of Haskell, including its genesis and principles, technical contributions, implementations and tools, and applications and impact.},
+booktitle = {Proceedings of the Third ACM SIGPLAN Conference on History of Programming Languages},
+pages = {12–1–12–55},
+location = {San Diego, California},
+series = {HOPL III}
+}

src/Case_Studies/cardano-regression.rst

@@ -42,10 +42,10 @@ interpreter. In klister, there are 4 major subsystem:
 
 #. Parser: The system that lexes and tokenizes. Klister employs |MegaParsec| for
    its parser.
-#. Expander: Klister is a scheme-like language with hygenic macros. This
+#. Expander: klister is a scheme-like language with hygenic macros. This
    subsystem performs the macro expansion and elaboration typical to these
    kinds of programming languages.
-#. Type Checker: Klister is a pure functional language with Hindley-Milner type
+#. Type Checker: klister is a pure functional language with Hindley-Milner type
    checking and higher-ordered types, including type safe macros. This subsystem
    type checks klister code.
 #. Evaluator: The evaluator inputs an abstract syntax tree which represents a

src/Case_Studies/klister.rst

@@ -1,4 +1,4 @@
-.. _Core:
+.. _Reading Core:
 
 :lightgrey:`Reading Core`
 =========================

src/Measurement_Observation/Direct_Observation/core.rst

@@ -1,4 +1,4 @@
-.. Stg
+.. _Reading Stg:
 
 :lightgrey:`Reading Stg`
 ========================

src/Measurement_Observation/Direct_Observation/stg.rst

@@ -234,7 +234,8 @@ Glossary
       in a ``let``, then these expressions would be duplicated *and* would be
       captured in an additionally allocated closure unnecessarily. Join points
       avoid these problems and are particularly relevant for Stream
-      :term:`Fusion` performance.
+      :term:`Fusion` performance. For more see the join points paper:
+      :cite:t:`compilingWithoutCont`.
 
    Known Function