diff options
author | buggymcbugfix <mail@vilem.net> | 2020-05-12 00:59:28 +0300 |
---|---|---|
committer | Marge Bot <ben+marge-bot@smart-cactus.org> | 2020-05-21 12:18:06 -0400 |
commit | 3451584f98d4a6b26dba4079b9a703e70a49a3ab (patch) | |
tree | d827d967bec8d406b26cec7e7a97b0e4f2d95ca4 /libraries | |
parent | 6890c38d4568ca444cccc47dd1a86c5e020c3521 (diff) | |
download | haskell-3451584f98d4a6b26dba4079b9a703e70a49a3ab.tar.gz |
Fix spelling mistakes and typos
Diffstat (limited to 'libraries')
-rw-r--r-- | libraries/base/GHC/List.hs | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/libraries/base/GHC/List.hs b/libraries/base/GHC/List.hs index 3215f12b5b..0af80801ae 100644 --- a/libraries/base/GHC/List.hs +++ b/libraries/base/GHC/List.hs @@ -277,10 +277,10 @@ to list-producing functions abstracted over cons and nil. Here we call them FB functions because their names usually end with 'FB'. It's a good idea to inline FB functions because: -* They are higher-order functions and therefore benefits from inlining. +* They are higher-order functions and therefore benefit from inlining. * When the final consumer is a left fold, inlining the FB functions is the only - way to make arity expansion to happen. See Note [Left fold via right fold]. + way to make arity expansion happen. See Note [Left fold via right fold]. For this reason we mark all FB functions INLINE [0]. The [0] phase-specifier ensures that calls to FB functions can be written back to the original form |