Skip to content
GitLab
Projects
Groups
Snippets
/
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Sign in / Register
Toggle navigation
Menu
Open sidebar
Shayne Fletcher
Glasgow Haskell Compiler
Commits
9491fea2
Commit
9491fea2
authored
Aug 29, 2014
by
Gabor Greif
💬
Browse files
Typos in comments
parent
fa9dd067
Changes
5
Hide whitespace changes
Inline
Side-by-side
compiler/deSugar/DsBinds.lhs
View file @
9491fea2
...
...
@@ -694,7 +694,7 @@ drop_dicts drops dictionary bindings on the LHS where possible.
will be simple NonRec bindings. We don't handle recursive
dictionaries!
NB3: In the common case of a non-overloaded, but perh
p
as-polymorphic
NB3: In the common case of a non-overloaded, but perha
p
s-polymorphic
specialisation, we don't need to bind *any* dictionaries for use
in the RHS. For example (Trac #8331)
{-# SPECIALIZE INLINE useAbstractMonad :: ReaderST s Int #-}
...
...
compiler/rename/RnPat.lhs
View file @
9491fea2
...
...
@@ -527,7 +527,7 @@ rnHsRecFields ctxt mk_arg (HsRecFields { rec_flds = flds, rec_dotdot = dotdot })
; dotdot_flds <- rn_dotdot dotdot mb_con flds1
-- Check for an empty record update e {}
-- NB: don't complain about e { .. }, bec
u
ase rn_dotdot has done that already
-- NB: don't complain about e { .. }, beca
u
se rn_dotdot has done that already
; case ctxt of
HsRecFieldUpd | Nothing <- dotdot
, null flds
...
...
compiler/simplCore/CSE.lhs
View file @
9491fea2
...
...
@@ -108,9 +108,9 @@ INLINE or NOINLINE. (Examples from Roman Leshchinskiy.) Consider
bar = foo yes
We do not expect the rule to fire. But if we do CSE, then we risk
getting yes=no, and the rule does fire. Actually, it won't bec
u
ase
getting yes=no, and the rule does fire. Actually, it won't beca
u
se
NOINLINE means that 'yes' will never be inlined, not even if we have
yes=no. So that's fine (now; perh
p
as in the olden days, yes=no would
yes=no. So that's fine (now; perha
p
s in the olden days, yes=no would
have substituted even if 'yes' was NOINLINE.
But we do need to take care. Consider
...
...
compiler/typecheck/TcEnv.lhs
View file @
9491fea2
...
...
@@ -426,7 +426,7 @@ Note especially that
* It does not extend the local RdrEnv (tcl_rdr), because the things are
already in the GlobalRdrEnv. Extending the local RdrEnv isn't terrible,
but it means there is an entry for the same Name in both global and local
RdrEnvs, and that lead to duplicate "perh
p
as you meant..." suggestions
RdrEnvs, and that lead to duplicate "perha
p
s you meant..." suggestions
(e.g. T5564).
We don't bother with the tcl_th_bndrs environment either.
...
...
docs/users_guide/glasgow_exts.xml
View file @
9491fea2
...
...
@@ -5358,7 +5358,7 @@ is extended thus: defaulting applies when all the unresolved constraints involve
</para></listitem>
</itemizedlist>
So, for example, the expression
<literal>
length "foo"
</literal>
will give rise
to an ambiguous use of
<literal>
IsString a0
</literal>
which, bec
u
ase of the above
to an ambiguous use of
<literal>
IsString a0
</literal>
which, beca
u
se of the above
rules, will default to
<literal>
String
</literal>
.
</para>
<para>
...
...
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment