- 27 Apr, 2012 2 commits
-
-
pcapriotti authored
-
pcapriotti authored
-
- 12 Apr, 2012 1 commit
-
-
dterei authored
-
- 04 Apr, 2012 1 commit
-
-
Simon Peyton Jones authored
-
- 28 Mar, 2012 1 commit
-
-
dterei authored
No reason user should turn them off, just want for ghc developer debugging uses.
-
- 23 Mar, 2012 4 commits
- 27 Feb, 2012 2 commits
-
-
Simon Marlow authored
And make the docs a bit more concrete.
-
Simon Marlow authored
-
- 10 Feb, 2012 1 commit
-
-
Simon Peyton Jones authored
-
- 12 Jan, 2012 1 commit
-
-
Simon Peyton Jones authored
This patch implements the idea of deferring (most) type errors to runtime, instead emitting only a warning at compile time. The basic idea is very simple: * The on-the-fly unifier in TcUnify never fails; instead if it gets stuck it emits a constraint. * The constraint solver tries to solve the constraints (and is entirely unchanged, hooray). * The remaining, unsolved constraints (if any) are passed to TcErrors.reportUnsolved. With -fdefer-type-errors, instead of emitting an error message, TcErrors emits a warning, AND emits a binding for the constraint witness, binding it to (error "the error message"), via the new form of evidence TcEvidence.EvDelayedError. So, when the program is run, when (and only when) that witness is needed, the program will crash with the exact same error message that would have been given at compile time. Simple really. But, needless to say, the exercise forced me into some major refactoring. * TcErrors is almost entirely rewritten * EvVarX and WantedEvVar have gone away entirely * ErrUtils is changed a bit: * New Severity field in ErrMsg * Renamed the type Message to MsgDoc (this change touches a lot of files trivially) * One minor change is that in the constraint solver we try NOT to combine insoluble constraints, like Int~Bool, else all such type errors get combined together and result in only one error message! * I moved some definitions from TcSMonad to TcRnTypes, where they seem to belong more
-
- 07 Jan, 2012 1 commit
-
-
Ian Lynagh authored
-
- 03 Jan, 2012 1 commit
-
-
Simon Marlow authored
Modified version of a patch by shelarcy <shelarcy@gmail.com>
-
- 06 Dec, 2011 1 commit
-
-
Simon Marlow authored
At present the number of capabilities can only be *increased*, not decreased. The latter presents a few more challenges!
-
- 22 Nov, 2011 1 commit
-
-
dterei authored
-
- 21 Nov, 2011 2 commits
- 16 Nov, 2011 1 commit
-
-
Simon Peyton Jones authored
I did a bit of refactoring (of course) at the same time. See the discussion in Trac #5587. Most of the real change is in CoreArity.
-
- 09 Nov, 2011 1 commit
-
-
- 29 Sep, 2011 1 commit
-
-
Simon Peyton Jones authored
-
- 31 May, 2011 3 commits
-
-
- 25 May, 2011 1 commit
-
-
Simon Marlow authored
-
- 16 Apr, 2011 1 commit
-
-
Ian Lynagh authored
-
- 04 Apr, 2011 1 commit
-
-
Ian Lynagh authored
-
- 29 Mar, 2011 1 commit
-
-
Ian Lynagh authored
-
- 01 Feb, 2011 1 commit
-
-
Simon Marlow authored
It is still (silently) accepted for backwards compatibility.
-
- 28 Jan, 2011 1 commit
-
-
simonpj@microsoft.com authored
-
- 27 Jan, 2011 1 commit
-
-
simonpj@microsoft.com authored
The changes are: * New flag -fwarn-incomplete-uni-patterns, which checks for incomplete patterns in (a) lambdas, (b) pattern bindings * New flag is not implied by -W or -Wall (too noisy; and many libraries use incomplete pattern bindings) * Actually do the incomplete-pattern check for pattern bindings (previously simply omitted) * Documentation for new flag
-
- 01 Dec, 2010 1 commit
-
-
Simon Marlow authored
-
- 06 Mar, 2011 2 commits
-
-
Ian Lynagh authored
-
simonpj@microsoft.com authored
Also change the behaviour slightly, to warn only for *unqualified* imports. See Trac #4977.
-
- 16 Nov, 2010 2 commits
-
-
simonpj@microsoft.com authored
-
simonpj@microsoft.com authored
See Trac #4488. The basic idea is to check for fun :: ty -> ty where fun is one of toIntegerName toRationalName fromIntegralName realToFracName There's a (documented) flag to control it -fwarn-identities. Currently -Wall switches it on.
-
- 14 Nov, 2010 1 commit
-
-
Ian Lynagh authored
They said: (NOTE: not supported since GHC 4.x. Please ask if you're interested in this.)
-
- 13 Oct, 2010 1 commit
-
-
Simon Marlow authored
-
- 22 Sep, 2010 1 commit
-
-
simonpj@microsoft.com authored
This makes \(x:xs) -> e want when you have -fwarn-incomplete-patterns, which is consistent.
-