Inline `Settings` into `DynFlags`
After the previous commit, `Settings` is just a thin wrapper around other groups of settings. While `Settings` is used by GHC-the-executable to initalize `DynFlags`, in principle another consumer of GHC-the-library could initialize `DynFlags` a different way. It therefore doesn't make sense for `DynFlags` itself (library code) to separate the settings that typically come from `Settings` from the settings that typically don't.
Showing
- compiler/cmm/CLabel.hs 7 additions, 7 deletionscompiler/cmm/CLabel.hs
- compiler/cmm/CmmInfo.hs 1 addition, 1 deletioncompiler/cmm/CmmInfo.hs
- compiler/cmm/CmmType.hs 4 additions, 4 deletionscompiler/cmm/CmmType.hs
- compiler/deSugar/DsForeign.hs 1 addition, 1 deletioncompiler/deSugar/DsForeign.hs
- compiler/ghci/Linker.hs 1 addition, 1 deletioncompiler/ghci/Linker.hs
- compiler/main/CodeOutput.hs 2 additions, 2 deletionscompiler/main/CodeOutput.hs
- compiler/main/DriverPipeline.hs 11 additions, 10 deletionscompiler/main/DriverPipeline.hs
- compiler/main/DynFlags.hs 109 additions, 85 deletionscompiler/main/DynFlags.hs
- compiler/main/GhcMake.hs 2 additions, 2 deletionscompiler/main/GhcMake.hs
- compiler/main/SysTools.hs 2 additions, 2 deletionscompiler/main/SysTools.hs
- ghc/GHCi/Leak.hs 1 addition, 2 deletionsghc/GHCi/Leak.hs
- includes/MachDeps.h 1 addition, 1 deletionincludes/MachDeps.h
- utils/deriveConstants/Main.hs 4 additions, 4 deletionsutils/deriveConstants/Main.hs
Loading
Please register or sign in to comment