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

users-guide: Fix PtrRepLifted to LiftedRep

Fix `TYPE 'PtrRepLifted` to `TYPE 'LiftedRep`

[ci skip]

Test Plan: build

Reviewers: bgamari

Reviewed By: bgamari

Subscribers: rwbarton, thomie, carter

Differential Revision: https://phabricator.haskell.org/D4818
parent 5f5d0c9d
...@@ -156,7 +156,7 @@ kind ``TYPE 'IntRep`` and ``Double#`` has kind ``TYPE 'DoubleRep``. These ...@@ -156,7 +156,7 @@ kind ``TYPE 'IntRep`` and ``Double#`` has kind ``TYPE 'DoubleRep``. These
kinds say that the runtime representation of an ``Int#`` is a machine integer, kinds say that the runtime representation of an ``Int#`` is a machine integer,
and the runtime representation of a ``Double#`` is a machine double-precision and the runtime representation of a ``Double#`` is a machine double-precision
floating point. In contrast, the kind ``*`` is actually just a synonym floating point. In contrast, the kind ``*`` is actually just a synonym
for ``TYPE 'PtrRepLifted``. More details of the ``TYPE`` mechanisms appear in for ``TYPE 'LiftedRep``. More details of the ``TYPE`` mechanisms appear in
the `section on runtime representation polymorphism <#runtime-rep>`__. the `section on runtime representation polymorphism <#runtime-rep>`__.
   
Given that ``Int#``'s kind is not ``*``, it then it follows that Given that ``Int#``'s kind is not ``*``, it then it follows that
......
...@@ -806,7 +806,7 @@ messages and in GHCi: ...@@ -806,7 +806,7 @@ messages and in GHCi:
When :ghc-flag:`-fprint-explicit-runtime-reps` is enabled, GHC prints When :ghc-flag:`-fprint-explicit-runtime-reps` is enabled, GHC prints
``RuntimeRep`` type variables for levity-polymorphic types. ``RuntimeRep`` type variables for levity-polymorphic types.
Otherwise GHC will default these to ``PtrRepLifted``. For example, Otherwise GHC will default these to ``LiftedRep``. For example,
.. code-block:: none .. code-block:: none
......
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