[GHC] #5753: ghci doesn't always use compiled modules

[GHC]

#5753: ghci doesn't always use compiled modules
-----------------------+----------------------------------------------------
  Reporter:  rl        |          Owner:                  
      Type:  bug       |         Status:  closed          
  Priority:  normal    |      Milestone:  7.4.1           
 Component:  Compiler  |        Version:  7.2.1           
Resolution:  invalid   |       Keywords:                  
        Os:  Windows   |   Architecture:  Unknown/Multiple
   Failure:  Other     |     Difficulty:  Unknown         
  Testcase:            |      Blockedby:                  
  Blocking:            |        Related:                  
-----------------------+----------------------------------------------------
Changes (by rl):

  * status:  infoneeded => closed
  * resolution:  => invalid


Comment:

 Gosh, it turns out that for some reason, Cygwin's clock can be a couple of
 minutes ahead of the system clock so touching T.hs produces a timestamp in
 the future (based on Cygwin's clock) and even after recompiling, T.o has a
 timestamp before that (based on the system clock). So this indeed only
 happens under Cygwin and only under quite specific circumstances (although
 it seems that I'm not the only one for whom this happens).

 I'll close the ticket but have you considered storing an hash of the
 source file in the .hi file and using that instead of the timestamps? It
 seems that would be more robust.

-- 
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/5753#comment:6>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler