1. 28 Apr, 2009 3 commits
  2. 29 Apr, 2009 4 commits
  3. 28 Apr, 2009 7 commits
  4. 27 Apr, 2009 6 commits
  5. 26 Apr, 2009 3 commits
  6. 25 Apr, 2009 1 commit
  7. 24 Apr, 2009 8 commits
  8. 23 Apr, 2009 6 commits
  9. 21 Apr, 2009 2 commits
    • Simon Marlow's avatar
    • Simon Marlow's avatar
      FIX #2682: banish silly cases of the "module Foo is not loaded" error · ef03a76a
      Simon Marlow authored
      In GHCi if you say 'import Foo' meaning to load a package module Foo,
      and Foo.hs is found on the search path, then GHCi replies "module Foo
      is not loaded", because it knows Foo refers to the source file rather
      than the package module, and you haven't loaded that module with
      :load.
      
      This is consistent with the usual module-finding semantics.  However,
      it isn't particularly useful.  And it leads to silly problems like not
      being able to start GHCi when you happen to be sitting in
      libraries/base, because GHCi thinks the Prelude hasn't been loaded.
      
      So now I've made a slight change to the way that 'import M' works: if
      M is loaded, then it refers to the loaded module, otherwise it looks
      for a package module M.  This does what the reporter of #2682 wanted,
      and since it turns an error condition into meaningful behaviour it
      can't break anything.  
      
      The only undesirable consequence is that 'import M' might refer to a
      different M than ':load M'.  Hopefully that won't lead to confusion.
      ef03a76a