#7231: GHCi erroneously unloads modules after a failed :reload -------------------------------------+------------------------------------- Reporter: parcs | Owner: simonmar Type: bug | Status: closed Priority: high | Milestone: 7.6.2 Component: GHCi | Version: 7.6.1 Resolution: fixed | Keywords: Operating System: Unknown/Multiple | Architecture: Type of failure: Compile-time | Unknown/Multiple performance bug | Test Case: Blocked By: | Blocking: Related Tickets: | Differential Rev(s): Wiki Page: | -------------------------------------+------------------------------------- Comment (by nh2): From over at https://ghc.haskell.org/trac/ghc/ticket/12935#comment:14, I found that this change is what makes the `[3 of 4]` order of `ghc --make` dependent on file mtime and thus generates different output depending on whether or not your resume a build. Could somebody shortly explain to me what the use case of the functionality that was broken and fixed in this issue is? Is it important that in ghci you can already use imports from the non- broken module imports while other imports are still broken? I'm asking because I'd imagine you'd first fix all imports anyway before you are doing anything sensible in the module, or am I wrong? -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/7231#comment:9 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler