summaryrefslogtreecommitdiff
path: root/docs/users_guide/using-warnings.rst
diff options
context:
space:
mode:
authorJoachim Breitner <mail@joachim-breitner.de>2016-09-24 09:16:59 +0900
committerJoachim Breitner <mail@joachim-breitner.de>2016-09-24 09:19:32 +0900
commit68f72f101d67b276aff567be03619a3fd9618017 (patch)
tree3ab35a6e7128daa45d778f590a1f037fa1094a5b /docs/users_guide/using-warnings.rst
parentd122935340ddf97a5a8496070de1f9bb34328440 (diff)
downloadhaskell-68f72f101d67b276aff567be03619a3fd9618017.tar.gz
Replace INLINEABLE by INLINABLE (#12613)
as the latter is the official, correct spelling, and the former just a misspelling accepted by GHC. Also document in the user’s guide that the alternative spelling is accepted This commit was brough to you by HIW 2016.
Diffstat (limited to 'docs/users_guide/using-warnings.rst')
-rw-r--r--docs/users_guide/using-warnings.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/users_guide/using-warnings.rst b/docs/users_guide/using-warnings.rst
index 8b5e704d85..c07058a4ef 100644
--- a/docs/users_guide/using-warnings.rst
+++ b/docs/users_guide/using-warnings.rst
@@ -201,12 +201,12 @@ of ``-W(no-)*``.
-Wall-missed-specialisations
Emits a warning if GHC cannot specialise an overloaded function, usually
- because the function needs an ``INLINEABLE`` pragma. The "all" form reports
+ because the function needs an ``INLINABLE`` pragma. The "all" form reports
all such situations whereas the "non-all" form only reports when the
situation arises during specialisation of an imported function.
The "non-all" form is intended to catch cases where an imported function
- that is marked as ``INLINEABLE`` (presumably to enable specialisation) cannot
+ that is marked as ``INLINABLE`` (presumably to enable specialisation) cannot
be specialised as it calls other functions that are themselves not specialised.
Note that these warnings will not throw errors if used with :ghc-flag:`-Werror`.