Emily
@matheus23 thanks for the initial idea! ~It's all your fault~ I enjoyed sketching this out.
Further _still_, this provides a cleaner path for backwards-incompatible changes to builtins. Let's say that for some silly reason we have to change the behavior of `Text/show`. Standard v10 calls...
It also looks like turning keywords/operators into untyped builtins will kill a lot of normalization opportunities – e.g. `"a" ++ "b"` can't be normalized to `"ab"` if `++` is defined...
With haskell-src-exts-1.19.1 everything works just fine (you need `LambdaCase` as well, though): ``` haskell {-# LANGUAGE EmptyCase, LambdaCase #-} x = \case{} ``` I can confirm that the standard build...
Btw, you already can get multiline imports: https://github.com/jaspervdj/stylish-haskell/blob/master/data/stylish-haskell.yaml#L67-L88.
An example for future reference: ``` {-# LANGUAGE Unsafe #-} module Main where import safe Safe main :: IO () main = putStrLn "Hello, World!" ```
@afcowie is this issue still relevant?
It also happens with comments in the middle of `import` statements, e.g. https://github.com/jaspervdj/stylish-haskell/issues/151: ```haskell {-# OPTIONS_GHC -F -pgmF htfpp #-} module Main where import Test.Framework import Test.Framework.BlackBoxTest import {-@ HTF_TESTS...
This might be related: https://github.com/jaspervdj/stylish-haskell/issues/51#issuecomment-30278481.
So the wiki is the source of truth and /docs is effectively a read-only mirror? Or are changes from /docs going to be backported every release? On Jan 30 2019,...