Better language extensions/warnings (fixes #85)

Author: snoyberg

etc/template/package.yaml

@@ -23,17 +23,24 @@ dependencies:
 - base >= 4.10 && < 10
 - rio >= 0.1.1.0
 
+ghc-options:
+- -Wall
+- -Wcompat
+- -Wincomplete-record-updates
+- -Wincomplete-uni-patterns
+- -Wredundant-constraints
+
+- -threaded
+- -rtsopts
+- -with-rtsopts=-N
+
 library:
   source-dirs: src
 
 executables:
   PROJECTNAME-exe:
     main:                Main.hs
     source-dirs:         app
-    ghc-options:
-    - -threaded
-    - -rtsopts
-    - -with-rtsopts=-N
     dependencies:
     - PROJECTNAME
     - optparse-simple
@@ -42,10 +49,6 @@ tests:
   PROJECTNAME-test:
     main:                Spec.hs
     source-dirs:         test
-    ghc-options:
-    - -threaded
-    - -rtsopts
-    - -with-rtsopts=-N
     dependencies:
     - PROJECTNAME
     - hspec

rio/README.md

@@ -152,6 +152,7 @@ GeneralizedNewtypeDeriving
 InstanceSigs
 KindSignatures
 LambdaCase
+MonadFailDesugaring
 MultiParamTypeClasses
 MultiWayIf
 NamedFieldPuns
@@ -178,6 +179,8 @@ Notes on some surprising choices:
 * Despite the fact that `OverloadedStrings` can break existing code,
   we recommend its usage to encourage avoidance of the `String` data
   type. Also, for new code, the risk of breakage is much lower.
+* `MonadFailDesugaring` helps prevent partial pattern matches in your
+  code, see [#85](https://github.com/commercialhaskell/rio/issues/85)
 
 __TODO__ Do we recommend setting in `package.yaml` or in the source
 files themselves? Need to discuss and come to a conclusion on this