summaryrefslogtreecommitdiff
path: root/doc/todo/Add_MonadBaseControl_instance_to_Propellor/comment_1_4b0cd7acc6442210a80c547981b5ae45._comment
blob: b38a015f83da0dc71ac813f012afa854182b618b (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
[[!comment format=mdwn
 username="joey"
 subject="""comment 1"""
 date="2016-11-30T21:07:26Z"
 content="""
I'm not entirely opposed to it, but this does add another two
dependencies that have to be installed on every host managed by propellor.

Also, I don't really understand the instance MonadBaseControl
implementation. (And have always had that difficulty with
monad-control, which is one of the reasons I've stopped using it.)
This and not having anything to test it with makes me fear maintaining it.

It looks like it would be sufficient make Propellor derive MonadBase IO,
and then the MonadBaseControl instance could be shipped in another
package (or even implemented in your config.hs). Does that sound like a
reasonable compromise?
"""]]