[Git][ghc/ghc][master] Minor spelling fixes to users guide.
Marge Bot
gitlab at gitlab.haskell.org
Wed May 29 14:37:20 UTC 2019
Marge Bot pushed to branch master at Glasgow Haskell Compiler / GHC
Commits:
32acecc2 by P.C. Shyamshankar at 2019-05-29T14:37:16Z
Minor spelling fixes to users guide.
- - - - -
8 changed files:
- docs/users_guide/bugs.rst
- docs/users_guide/debug-info.rst
- docs/users_guide/editing-guide.rst
- docs/users_guide/ghci.rst
- docs/users_guide/phases.rst
- docs/users_guide/separate_compilation.rst
- docs/users_guide/using-optimisation.rst
- docs/users_guide/using-warnings.rst
Changes:
=====================================
docs/users_guide/bugs.rst
=====================================
@@ -435,7 +435,7 @@ undefined or implementation specific in Haskell 98.
architecture; in other words it holds 32 bits on a 32-bit machine,
and 64-bits on a 64-bit machine.
- Arithmetic on ``Int`` is unchecked for overflowoverflow\ ``Int``, so
+ Arithmetic on ``Int`` is unchecked for overflow\ ``Int``, so
all operations on ``Int`` happen modulo 2\ :sup:`⟨n⟩` where ⟨n⟩ is
the size in bits of the ``Int`` type.
=====================================
docs/users_guide/debug-info.rst
=====================================
@@ -145,7 +145,7 @@ this point in the program,
other language-agnostic debugging tools, GHC is forced to heuristically
choose one location from among this set.
- For this reason we should be cautious when interpretting the source locations
+ For this reason we should be cautious when interpreting the source locations
provided by GDB. While these locations will usually be in some sense
"correct", they aren't always useful. This is why profiling tools targetting
Haskell should supplement the standard source location information with
=====================================
docs/users_guide/editing-guide.rst
=====================================
@@ -214,7 +214,7 @@ External links can be written in either of these ways,
To core library Haddock documentation
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-It is often useful to be able to refer to the Haddock documention of the
+It is often useful to be able to refer to the Haddock documentation of the
libraries shipped with GHC. The users guide's build system provides
commands for referring to documentation for the following core GHC packages,
=====================================
docs/users_guide/ghci.rst
=====================================
@@ -2212,7 +2212,7 @@ commonly used commands.
This output shows that, in the context of the current session (ie
in the scope of ``Prelude``), the first group of items from
- ``Data.Maybe`` are not in scope (althought they are available in
+ ``Data.Maybe`` are not in scope (although they are available in
fully qualified form in the GHCi session - see
:ref:`ghci-scope`), whereas the second group of items are in
scope (via ``Prelude``) and are therefore available either
=====================================
docs/users_guide/phases.rst
=====================================
@@ -1019,7 +1019,7 @@ for example).
:type: dynamic
:category: linking
- On Windows, GHC normally generates a manifestmanifest file when
+ On Windows, GHC normally generates a manifest file when
linking a binary. The manifest is placed in the file
:file:`{prog}.exe.manifest`` where ⟨prog.exe⟩ is the name of the
executable. The manifest file currently serves just one purpose: it
=====================================
docs/users_guide/separate_compilation.rst
=====================================
@@ -586,7 +586,7 @@ The GHC API exposes functions for reading and writing these files.
:type: dynamic
:category: extended-interface-files
- Writes out extended interface files alongisde regular enterface files.
+ Writes out extended interface files alongside regular interface files.
Just like regular interface files, GHC has a recompilation check to detect
out of date or missing extended interface files.
=====================================
docs/users_guide/using-optimisation.rst
=====================================
@@ -316,7 +316,7 @@ by saying ``-fno-wombat``.
Enables the common-sub-expression elimination optimisation on the STG
intermediate language, where it is able to common up some subexpressions
- that differ in their types, but not their represetation.
+ that differ in their types, but not their representation.
.. ghc-flag:: -fdicts-cheap
:shortdesc: Make dictionary-valued expressions seem cheap to the optimiser.
=====================================
docs/users_guide/using-warnings.rst
=====================================
@@ -215,7 +215,7 @@ all these warnings can still be controlled with ``-f(no-)warn-*`` instead
of ``-W(no-)*``.
.. ghc-flag:: -Wunrecognised-warning-flags
- :shortdesc: throw a warning when an unreconised ``-W...`` flag is
+ :shortdesc: throw a warning when an unrecognised ``-W...`` flag is
encountered on the command line.
:type: dynamic
:reverse: -Wno-unrecognised-warning-flags
View it on GitLab: https://gitlab.haskell.org/ghc/ghc/commit/32acecc29d4766fd2b168cbd654667ba6be03dbb
--
View it on GitLab: https://gitlab.haskell.org/ghc/ghc/commit/32acecc29d4766fd2b168cbd654667ba6be03dbb
You're receiving this email because of your account on gitlab.haskell.org.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-commits/attachments/20190529/770637d2/attachment-0001.html>
More information about the ghc-commits
mailing list