Boldizsár Németh

I think there is some mistake. The [actual sources](http://hackage.haskell.org/package/haskell-tools-builtin-refactorings-1.0.1.1/src/Language/Haskell/Tools/Refactor/Builtin/OrganizeImports.hs) uploaded to hackage as `haskell-tools-builtin-refactorings-1.0.1.1` does not match the compiler errors provided here.

It would also enable to set the packageId of different packages.

This causes another problem in the `fay-dom-0.5.0.1` and `fay-jquery-0.6.1.0` packages: they use the `fay-base` package instead of a base, but have a `Path_` module. The path module would need base...

Walkaround: - Don't use libraries that define a `Prelude` module. - Don't have modules with the same qualified name (in different components). - Don't use keywords that can be restricted...

If we could create a version of `load` that does not reload certain modules it would be possible to use different flags for different packages.

``` f a b = (a,b) g = map (f 3) [1,2,3] ``` ``` f b a = (a,b) g = map (\x -> f x 3) [1,2,3] ```

The definition of the name (in the signature) was marked as not found in `haskell-names`. The same with `traverse-with-class`.

Hmm, interesting. Haskell Tools reads the information about extensions from the module summary, not the syntax tree, so it should not trigger for names in the source code. Can you...

It seems that the `mkTime` template haskell function causes these segfaults. Removing it from the code solves the issues.

The problem seems to be related to the following GHC bug: https://ghc.haskell.org/trac/ghc/ticket/13112. In short, this is caused when Template Haskell code is placed on a memory address above 2GB. **Walkaround**:...