#5317: non-linear complexity of :reload combined with :module in ghci
---------------------------+------------------------------------------------
Reporter: SimonHengel | Owner:
Type: bug | Status: closed
Priority: normal | Milestone: 7.4.1
Component: Compiler | Version: 7.0.3
Resolution: wontfix | Keywords:
Testcase: | Blockedby:
Difficulty: | Os: Unknown/Multiple
Blocking: | Architecture: Unknown/Multiple
Failure: None/Unknown |
---------------------------+------------------------------------------------
Changes (by simonmar):
* status: new => closed
* resolution: => wontfix
Comment:
It's faster in 7.2 as a result of my changes in
5cd39aa33f970ff42e22b1c9c73502e4229dc488
{{{
Author: Simon Marlow <[email protected]>
Date: Sat Jun 4 00:13:04 2011 +0100
Tidy up the ic_exports field of the InteractiveContext. Previously
was [(Module, Maybe ImportDecl)], now it is just [ImportDecl]. So now
":m +A" and "import A" do exactly the same thing in GHCi, and use the
same code paths.
}}}
The underlying problem remains, but is far less severe now. The problem
is this: we keep track of all the `:module` and `import` commands and
replay them after each `:reload`. The list is cleared by `:load` and a
few other things. It's not obvious to me if there's a good way to tell in
general when you can remove items from the list.
I'm tempted to just punt on this. It won't be nearly as noticeable in 7.2
anyway.
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/5317#comment:2>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
