Andrey Mokhov

> The problem that I see is that the memory resource should be a global resource and consequently would need to be threaded throughout the build system. I'm not sure...

We could turn resources into expressions: ```haskell type Resources = DiffExpr [(Resource, Int)] -- We currently have these resource settings mixed with top-level Rules.hs definitions defaultResources :: Resources defaultResources =...

I agree this seems excessive at first sight, but if the user does want to tweak resources even for just a single file like `DynFlags` then it would be very...

@michalt Note, `MIN_VERSION_GLASGOW_HASKELL` is also set by Hadrian in `Rules.Generators.GhcVersionH`, so one option is to include the generated `includes/ghcversion.h` in addition to the Cabal macros headers. But simply passing it...

> Looking at the Lexer.hs, line 126: @michalt Stange. My `Lexer.hs` is different, this is line 126: ``` {-# LINE 1 "D:\\msys\\mingw64\\lib/include\\ghcversion.h" #-} ``` Could it be that you've rewritten...

@michalt Any further updates on this? I've just pushed quite a big refactoring/simplification, which could have messed up your uncommitted work (apologies if this is the case!). Let me know...

@michalt Thank you for pushing this forward. I think you are on the right track! Your GHC changes seem fine, hopefully `GLOBAL_VAR` will not stand in the way. > I'm...

> Cool, should we ping some GHC dev about this? (to see what they think about it ;-) Let me try :) @bgamari Have you got a minute to look...

@ndmitchell What's your opinion on the `newtype Path` proposal? Shall I proceed with the refactoring? This may be useful even if it turns out to be not on the critical...

Tried to make some progress with `newtype Path` but stumbled over the problem that I can't use `need` on a `Path` without doing `fromPath` first, which looks ugly... I could,...