Fix spelling of INLIN(E)ABLE in comments

The correct spelling is INLINABLE. It is confusing to read comments which refer to INLINEABLE.

How to fix this:

1. git grep INLINEABLE
2. Open all the files and change to INLINABLE.

Trac metadata

Trac field	Value
Version	8.0.1
Type	Task
TypeOfFailure	OtherFailure
Priority	lowest
Resolution	Unresolved
Component	Compiler
Test case
Differential revisions
BlockedBy
Related
Blocking
CC
Operating system
Architecture

changed weight to 0

added Ttask Trac import newcomer labels

JFTR: It’s not only in comments; it is used as pragmas in many files:

libraries/base/Control/Monad.hs:{-# INLINEABLE foldM #-}
libraries/base/Control/Monad.hs:{-# INLINEABLE foldM_ #-}
libraries/base/Control/Monad.hs:{-# INLINEABLE replicateM #-}
libraries/base/Control/Monad.hs:{-# INLINEABLE replicateM_ #-}
libraries/base/Control/Monad.hs:{-# INLINEABLE unless #-}
libraries/base/Control/Monad.hs:{-# INLINEABLE mfilter #-}
libraries/base/Data/Bits.hs:{-# INLINEABLE toIntegralSized #-}
libraries/base/GHC/Base.hs:{-# INLINEABLE liftA #-}
libraries/base/GHC/Base.hs:{-# INLINEABLE liftA2 #-}
libraries/base/GHC/Base.hs:{-# INLINEABLE liftA3 #-}
libraries/base/GHC/Base.hs:{-# INLINEABLE when #-}
libraries/base/GHC/Base.hs:{-# INLINEABLE liftM #-}
libraries/base/GHC/Base.hs:{-# INLINEABLE liftM2 #-}
libraries/base/GHC/Base.hs:{-# INLINEABLE liftM3 #-}
libraries/base/GHC/Base.hs:{-# INLINEABLE liftM4 #-}
libraries/base/GHC/Base.hs:{-# INLINEABLE liftM5 #-}
libraries/base/GHC/Base.hs:{-# INLINEABLE ap #-}
libraries/base/GHC/List.hs:{-# INLINEABLE maximum #-}
libraries/base/GHC/List.hs:{-# INLINEABLE minimum #-}
libraries/base/GHC/Real.hs:{-# INLINEABLE even #-}
libraries/base/GHC/Real.hs:{-# INLINEABLE odd  #-}

Are all these pragmas broken? No: Both are accepted by the lexer:

           ("inlinable", strtoken (\s -> (ITinline_prag s Inlinable FunLike))),
           ("inlineable", strtoken (\s -> (ITinline_prag s Inlinable FunLike))),
                                          -- Spelling variant

mentioned in commit 68f72f10

closed

Trac metadata

Trac field	Value
Resolution	Unresolved → ResolvedFixed

Thanks Joachim. My next question, why is INLINEABLE even accepted at all. We don't accept misspellings of other pragmas, why is this different?

FWIW, there are 996 spellings of INLINEABLE and 5773 spellings of INLINABLE on hackage.

added Plow label