#3217: Make GHCi have separate flags for interactive Haskell expressions
---------------------------------+------------------------------------------
Reporter: simonpj | Owner:
Type: feature request | Status: new
Priority: normal | Milestone: 6.12 branch
Component: Compiler | Version: 6.10.2
Severity: normal | Resolution:
Keywords: | Difficulty: Unknown
Testcase: | Os: Unknown/Multiple
Architecture: Unknown/Multiple |
---------------------------------+------------------------------------------
Comment (by claus):
Replying to [comment:11 simonpj]:
> ..conversation between Claus and Simon in detail; but it seems at least
that consensus has not been reached.
I thought consensus was fairly close:
- I'm no longer opposed to the change in principle
- I'm still slightly worried about the interface adding complexity
(perhaps it would suffice to document that `:set` corresponds to
commandline options while `:seti` corresponds to in-source pragmas, but it
would be better to make it so)
- Simon and I seemed to agree that this separation should be followed by
making the interactive options match the in-source options for the current
module
- we agreed that this would be easier to achieve if there was only one
`*`-ed module permitted per session (currently many such are permitted)
- we only disagreed on whether such a restriction might have negative
effects on other use cases; Simon strongly favoured this to avoid having
to define what it means for two modules to have compatible options; I
tended the other way, assuming it would be useful to have this defined
anyway
> * Claus, are you of the opinion that it'd be a retrograde step to
implement the original proposal of this ticket, without implementing some
version of your proposal? Or would it be a step in the right direction?
It would be a half step in the right direction. The only disadvantage I
can see is that without the other half step, the interim state might
actually be more complex (three sets of options to keep track of instead
of two). But as I said, I'm no longer opposed (just want more consistency
and less complexity;-).
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/3217#comment:14>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
