From b05f17de13f579268e9ae83d3bfa5efb7cb8be15 Mon Sep 17 00:00:00 2001 From: crumbtoo Date: Tue, 28 Nov 2023 12:19:04 -0700 Subject: [PATCH] fix link --- docs/src/commentary/layout-lexing.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/src/commentary/layout-lexing.rst b/docs/src/commentary/layout-lexing.rst index ee6241c..4fbfd5e 100644 --- a/docs/src/commentary/layout-lexing.rst +++ b/docs/src/commentary/layout-lexing.rst @@ -21,8 +21,7 @@ potential roadblocks on my mind before making an attempt were: * Context-sensitive keywords; Haskell allows for some words to be used as identifiers in appropriate contexts, such as :code:`family`, :code:`role`, :code:`as`. - Reading a note_ found in `GHC's lexer - `_, + Reading a note_ found in `GHC's lexer`_, it appears that keywords are only considered in bodies for which their use is relevant, e.g. :code:`family` and :code:`role` in type declarations, :code:`as` after :code:`case`; :code:`if`, :code:`then`, and :code:`else` in @@ -33,6 +32,7 @@ potential roadblocks on my mind before making an attempt were: section code in a way that *felt* different. .. _note: https://gitlab.haskell.org/ghc/ghc/-/wikis/commentary/coding-style#2-using-notes +.. _GHC's lexer: https://gitlab.haskell.org/ghc/ghc/-/blob/master/compiler/GHC/Parser/Lexer.x#L1133 After a bit of thought and research, whitespace sensitivity in the form of *layouts* as Haskell and I will refer to them as, are easily the scariest thing