| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Also a small formatting change in GHCi :help
|
|
|
|
|
| |
Authored-by: David Luposchainsky <dluposchainsky@gmail.com>
Signed-off-by: Austin Seipp <austin@well-typed.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit addresses #8051 by fixing
- Incorrect column indices reported in error messages for
single-line and multi-line input,
- incorrect line numbers reported in error messages for
expressions entered in multi-line input, and
- inhibiting the confusing interaction between `:{` and `:set +m`
causing the triggering of implicit multi-line continuation
mode right after `:}` terminates the multi-line entry block.
|
|\
| |
| |
| |
| |
| | |
Conflicts:
compiler/main/DynFlags.hs
compiler/utils/FastString.lhs
|
| |
| |
| |
| | |
Signed-off-by: Austin Seipp <aseipp@pobox.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
`:show paths` dumps the current working directory as well
as the current value of the `importPaths` dynamic flags field.
This addresses #8172
Signed-off-by: Herbert Valerio Riedel <hvr@gnu.org>
|
| | |
|
|/
|
|
|
| |
An unbuffered handle is very slow to output to and there doesn't seem to
be any reason to have these handles unbuffered.
|
|
|
|
|
|
|
| |
This restores the original behaviour that was broken accidentally during
the refactoring peformed via 4f764d06f3b9899c09a6a459a22d4be694ee45d9.
This has been broken effectively for all GHC 7.6.x releases.
|
|
|
|
|
|
| |
GHC >= 7.4 is needed to bootstrap.
Signed-off-by: Austin Seipp <aseipp@pobox.com>
|
|
|
|
|
|
|
| |
This commit also updates the GHC user guide section
regarding the `set prompt` command and closes #8047.
Signed-off-by: Herbert Valerio Riedel <hvr@gnu.org>
|
|
|
|
|
|
| |
It thought that .cmm files were Haskellish, but then didn't know
how to compile them. Now they aren't treated as Haskellish, and
it can compile and link them.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit changes the syntax and story around overlapping type
family instances. Before, we had "unbranched" instances and
"branched" instances. Now, we have closed type families and
open ones.
The behavior of open families is completely unchanged. In particular,
coincident overlap of open type family instances still works, despite
emails to the contrary.
A closed type family is declared like this:
> type family F a where
> F Int = Bool
> F a = Char
The equations are tried in order, from top to bottom, subject to
certain constraints, as described in the user manual. It is not
allowed to declare an instance of a closed family.
|
|
|
|
|
|
| |
Clang doesn't like whitespace between macro and arguments.
Signed-off-by: Austin Seipp <aseipp@pobox.com>
|
|
|
|
|
|
| |
Now that we share stdin with the program, we have to check for
handle-closed as well as EOF, as the program might have closed
stdin.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
- Remove unused property `def_prompt`.
|
|
|
|
|
| |
Now these are always added by the run<blah> functions in SysTools, so
we never miss any out. Several cleanups resulted.
|
|
|
|
| |
We now just pass the output filename as an argument instead
|
| |
|
|
|
|
| |
We now make the stage 2 compiler depend on GHC.Desugar.
|
|\ |
|
| |
| |
| |
| | |
v2: added a couple of comments
|
| |
| |
| |
| |
| | |
There were some cases where we weren't unsetting it when turning the
Dyn way on.
|
| | |
|
|/ |
|
|
|
|
|
|
|
| |
We now define _PROGNAME, and _PROG is automatically defined with
$(exeext). This will shortly automatically use the right exeext
depending on what stage it is being compiled with (exeext may be
different for different stages when cross-compiling).
|
| |
|
|
|
|
| |
and use them for split
|
| |
|
| |
|
|
|
|
|
| |
Thanks to Daniel Pratt <colorblinddad@gmail.com> for pointing out the failure
and fix.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This removes the '.PHONY' rule, so means that "make" in a built tree
won't repeat the check.
We also now check the .cabal files for the executables as well as the
libraries.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Function responsible for parsing the static flags, that were spread
across two modules (StaticFlags and StaticFlagParser), are now
in one file. This is analogous to dynamic flags parsing, which is
also contained within a single module.
Signed-off-by: David Terei <davidterei@gmail.com>
|
| |
|