Hello.
Here is one ghci feature that I find mildly annoying:
If ghci (re-)reads a module that contains some error,
then it considers the module loading as a complete failure,
and at the prompt I get the Prelude environment.
I'd like to have at least the import statements executed,
and possibly t
On Sat, Feb 16, 2008 at 10:53 AM, Johannes Waldmann
<[EMAIL PROTECTED]> wrote:
> If ghci (re-)reads a module that contains some error,
> then it considers the module loading as a complete failure,
> and at the prompt I get the Prelude environment.
>
> I'd like to have at least the import statem
On Sat, Feb 16, 2008 at 04:53:24PM +0100, Johannes Waldmann wrote:
> Hello.
>
> Here is one ghci feature that I find mildly annoying:
>
> If ghci (re-)reads a module that contains some error,
> then it considers the module loading as a complete failure,
> and at the prompt I get the Prelude envir
Sure.
Syntax errors are usually easy to spot and fix
(for the programmer who uses some reasonable code layout);
the motivation for my proposal was type errors.
I think it would be perfectly acceptable
if ghci rejects modules with parse errors (as it does now)
but handles modules with type errors
On Sat, Feb 16, 2008 at 06:58:29PM +0100, Johannes Waldmann wrote:
> Sure.
>
> Syntax errors are usually easy to spot and fix
> (for the programmer who uses some reasonable code layout);
> the motivation for my proposal was type errors.
>
> I think it would be perfectly acceptable
> if ghci rejec
PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
| Johannes Waldmann
| Sent: 16 February 2008 15:53
| To: glasgow-haskell-users@haskell.org
| Subject: ghci feature request: partially read modules
|
| Hello.
|
| Here is one ghci feature that I find mildly annoying:
|
| If ghci (re-)reads a module that con
