File tree Expand file tree Collapse file tree 1 file changed +10
-13
lines changed Expand file tree Collapse file tree 1 file changed +10
-13
lines changed Original file line number Diff line number Diff line change @@ -1278,29 +1278,26 @@ issues for Stackage maintenance.
12781278
12791279[:octicons-tag-24 : 2.1.1](https://github.com/commercialhaskell/stack/releases/tag/v2.1.1)
12801280
1281+ Default : ` true`
1282+
12811283When Stack notices that a new version of Stack is available, should it notify
12821284the user?
12831285
1284- ~~~yaml
1285- recommend-stack-upgrade : true
1286- ~~~
1287-
12881286# ## rebuild-ghc-options
12891287
12901288[:octicons-tag-24 : 0.1.6.0](https://github.com/commercialhaskell/stack/releases/tag/v0.1.6.0)
12911289
12921290Default : ` false`
12931291
1294- Should we rebuild a package when its GHC options change? Before Stack 0.1.6,
1295- this was a non-configurable `true`. However, in most cases, the flag is used to
1296- affect optimization levels and warning behavior, for which GHC itself doesn't
1297- actually recompile the modules anyway. Therefore, the new behavior is to not
1298- recompile on an options change, but this behavior can be changed back with the
1299- following :
1292+ Should Stack rebuild a package when its GHC options change?
13001293
1301- ~~~yaml
1302- rebuild-ghc-options : true
1303- ~~~
1294+ The default value reflects that, in most cases, GHC options are used to affect
1295+ optimization levels and warning behavior, for which GHC does not recompile the
1296+ modules.
1297+
1298+ !!! note
1299+
1300+ Before Stack 0.1.6.0, Stack rebuilt a package when its GHC options changed.
13041301
13051302# ## require-stack-version
13061303
You can’t perform that action at this time.
0 commit comments