Skip to content
  • Andreas Klebinger's avatar
    Give Uniq[D]FM a phantom type for its key. · c4de6a7a
    Andreas Klebinger authored and Marge Bot's avatar Marge Bot committed
    This fixes #17667 and should help to avoid such issues going forward.
    
    The changes are mostly mechanical in nature. With two notable
    exceptions.
    
    * The register allocator.
    
      The register allocator references registers by distinct uniques.
      However they come from the types of VirtualReg, Reg or Unique in
      various places. As a result we sometimes cast the key type of the
      map and use functions which operate on the now typed map but take
      a raw Unique as actual key. The logic itself has not changed it
      just becomes obvious where we do so now.
    
    * <Type>Env Modules.
    
    As an example a ClassEnv is currently queried using the types `Class`,
    `Name`, and `TyCon`. This is safe since for a distinct class value all
    these expressions give the same unique.
    
        getUnique cls
        getUnique (classTyCon cls)
        getUnique (className cls)
        getUnique (tcName $ classTyCon cls)
    
    This is for the most part contained within the modules defining the
    interface. However it requires us to play dirty when we are given a
    `Name` to lookup in a `UniqFM Class a` map. But again the logic did
    not change and it's for the most part hidden behind the Env Module.
    
    Some of these cases could be avoided by refactoring but this is left
    for future work.
    
    We also bump the haddock submodule as it uses UniqFM.
    c4de6a7a