diff options
| author | Joey Hess <joeyh@joeyh.name> | 2016-06-02 17:20:51 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2016-06-02 17:20:51 -0400 |
| commit | 65a7716a93960ea1418927bd9d4df22ad8fb9e21 (patch) | |
| tree | 7f11bdd0d5a5010b59b5ebb6bd0f8f0ea01247c0 | |
| parent | 460dc5f68852b0e5e7e55392fc0b48ed186bfcfd (diff) | |
include description in example
| -rw-r--r-- | doc/forum/recent_propellor_snapshots_cause_ghc_OOMs/comment_8_b20c69390343bf3b2a7f7b6776f43389._comment | 12 | ||||
| -rw-r--r-- | src/Propellor/EnsureProperty.hs | 2 |
2 files changed, 13 insertions, 1 deletions
diff --git a/doc/forum/recent_propellor_snapshots_cause_ghc_OOMs/comment_8_b20c69390343bf3b2a7f7b6776f43389._comment b/doc/forum/recent_propellor_snapshots_cause_ghc_OOMs/comment_8_b20c69390343bf3b2a7f7b6776f43389._comment new file mode 100644 index 00000000..df8c6222 --- /dev/null +++ b/doc/forum/recent_propellor_snapshots_cause_ghc_OOMs/comment_8_b20c69390343bf3b2a7f7b6776f43389._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 8""" + date="2016-06-02T21:04:33Z" + content=""" +@mithrandi there are ways to make ghc type error messages arbitrarily long, +and IIRC that causes the memory to blow up. + +I'm mostly interested in memory blowups when building a valid +configuration, since those cause problems to the hosts propellor is +deployed to, rather than just to the system where it's developed. +"""]] diff --git a/src/Propellor/EnsureProperty.hs b/src/Propellor/EnsureProperty.hs index ce01d436..c4666722 100644 --- a/src/Propellor/EnsureProperty.hs +++ b/src/Propellor/EnsureProperty.hs @@ -24,7 +24,7 @@ import Prelude -- Use `property'` to get the `OuterMetaTypesWithness`. For example: -- -- > foo = Property Debian --- > foo = property' $ \w -> do +-- > foo = property' "my property" $ \w -> do -- > ensureProperty w (aptInstall "foo") -- -- The type checker will prevent using ensureProperty with a property |