Commit b15136af authored by Takenobu Tani's avatar Takenobu Tani Committed by Ben Gamari
Browse files

user-guide: fix links and file names (fixes #13198)

There are some incorrect links and file names in GHC user's guide.

  * docs/users_guide/glasgow_exts.rst
    - GHC/Base.lhs
    - GHC/List.lhs

  * docs/users_guide/ffi-chap.rst
    - :base-ref:`Foreign`
    - :base-ref:`Control.Concurrent`

I fixed them.

Reviewers: austin, bgamari

Reviewed By: bgamari

Subscribers: thomie

Differential Revision: https://phabricator.haskell.org/D3035

GHC Trac Issues: #13198
parent 4dfc6d1c
......@@ -21,7 +21,7 @@ that programs using these features are not portable. Hence, these
features should be avoided where possible.
The FFI libraries are documented in the accompanying library
documentation; see for example the :base-ref:`Foreign` module.
documentation; see for example the :base-ref:`Foreign <Foreign.html>` module.
.. _ffi-ghcexts:
......@@ -569,7 +569,7 @@ where it is useful to have more control over which OS thread is used,
for example when calling foreign code that makes use of thread-local
state. For cases like this, we provide *bound threads*, which are
Haskell threads tied to a particular OS thread. For information on bound
threads, see the documentation for the :base-ref:`Control.Concurrent` module.
threads, see the documentation for the :base-ref:`Control.Concurrent <Control-Concurrent.html>` module.
Foreign exports and multi-threading
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
......
......@@ -13333,7 +13333,7 @@ Controlling what's going on in rewrite rules
great detail what rules are being fired. If you add :ghc-flag:`-dppr-debug`
you get a still more detailed listing.
- The definition of (say) ``build`` in ``GHC/Base.lhs`` looks like
- The definition of (say) ``build`` in ``GHC/Base.hs`` looks like
this: ::
build :: forall a. (forall b. (a -> b -> b) -> b -> b) -> [a]
......@@ -13346,10 +13346,10 @@ Controlling what's going on in rewrite rules
any inlining happening in the RHS of the ``INLINE`` thing. I regret
the delicacy of this.
- In ``libraries/base/GHC/Base.lhs`` look at the rules for ``map`` to
- In ``libraries/base/GHC/Base.hs`` look at the rules for ``map`` to
see how to write rules that will do fusion and yet give an efficient
program even if fusion doesn't happen. More rules in
``GHC/List.lhs``.
``GHC/List.hs``.
.. _special-ids:
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment