Commit 4f9df5a4 authored by Austin Seipp's avatar Austin Seipp

More release note touchups.

Signed-off-by: default avatarAustin Seipp <austin@well-typed.com>
parent b61958d7
......@@ -58,7 +58,7 @@
instances created other than the ones in its
definition.
For more information, see <xref linkend="closed-type-families"/>
For more information, see <xref linkend="closed-type-families"/>.
</para>
</listitem>
......@@ -70,7 +70,7 @@
increases the type safety of GHC, it is possible that some code
that previously compiled will no longer work.
For more information, see <xref linkend="roles"/>
For more information, see <xref linkend="roles"/>.
</para>
</listitem>
......@@ -79,7 +79,7 @@
GHC now supports overloading list literals using the new
<literal>OverloadedLists</literal> extension.
For more information, see <xref linkend="overloaded-lists"/>
For more information, see <xref linkend="overloaded-lists"/>.
</para>
</listitem>
......@@ -98,7 +98,7 @@
<para>
There has been significant overhaul of the type
inference engine and constraint solver, meaning it
should be faster and less memory intensive.
should be faster and use less memory.
</para>
</listitem>
......@@ -128,7 +128,7 @@
operations.
</para>
<para>
Note carefully: this is <em>only</em> available with
Note carefully: this is <emphasis>only</emphasis> available with
the LLVM backend, and should be considered
experimental.
</para>
......@@ -186,14 +186,14 @@
dynamic linker by default, instead of its built in
(static) object linker. This is more robust
cross-platform, and fixes many long-standing bugs (for
example, both constructors and destructors, weak
example: constructors and destructors, weak
symbols, etc work correctly, and several edge cases in
the RTS are fixed.)
</para>
<para>
As a result of this, GHCi (and Template Haskell) must
now load <em>dynamic</em> object files, not static
now load <emphasis>dynamic</emphasis> object files, not static
ones. To assist this, there is a new compilation flag,
<literal>-dynamic-too</literal>, which when used
during compilation causes GHC to emit both static and
......@@ -205,7 +205,7 @@
Note that Cabal will correctly handle
<literal>-dynamic-too</literal> for you automatically,
especially when <literal>-XTemplateHaskell</literal>
is needed - but you <em>must</em> tell Cabal you are
is needed - but you <emphasis>must</emphasis> tell Cabal you are
using the <literal>TemplateHaskell</literal>
extension.
</para>
......@@ -290,16 +290,16 @@
<literal>unsafe</literal>. An
<literal>interruptible</literal> foreign call is the
same as a <literal>safe</literal> call, but may be
interrupted by asynchronous <em>Haskell
exceptions</em>, such as those generated by
interrupted by asynchronous <emphasis>Haskell
exceptions</emphasis>, such as those generated by
<literal>throwTo</literal> or
<literal>timeout</literal>.
</para>
<para>
For more information, (including the exact details on
For more information (including the exact details on
how the foreign thread is interrupted,) see <xref
linkend="ffi-interruptible"/>
linkend="ffi-interruptible"/>.
</para>
</listitem>
......@@ -514,7 +514,7 @@
setting, which allows you to customize the
continuation prompt of multi-line input.
TODO FIXME: reference.
For more information, see <xref linkend="ghci-commands"/>.
</para>
</listitem>
<listitem>
......@@ -552,7 +552,7 @@
<itemizedlist>
<listitem>
<para>
Template Haskell now supports Roles (TODO FIXME: elaborate?)
Template Haskell now supports Roles.
</para>
</listitem>
<listitem>
......
......@@ -7672,13 +7672,13 @@ with <option>-XNoMonoLocalBinds</option> but type inference becomes less predica
<!-- ==================== End of type system extensions ================= -->
<sect1 id="typed-holes">
<title>Type Holes</title>
<title>Typed Holes</title>
<para>Type hole support is enabled with the option
<para>Typed hole support is enabled with the option
<option>-fwarn-typed-holes</option>, which is enabled by default.</para>
<para>
The goal of the type holes warning is not to change the type system, but to help with writing Haskell
The goal of the typed holes warning is not to change the type system, but to help with writing Haskell
code. Type holes can be used to obtain extra information from the type checker, which might otherwise be hard
to get.
Normally, the type checker is used to decide if a module is well typed or not. Using GHCi,
......
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