2016-12-07 19:13:52 +0000edvorg(~edvorg@host-46-50-214-114.bbcustomer.zsttk.net) (Ping timeout: 265 seconds)
2016-12-07 20:39:08 +0000hamishmack(~hamishmac@121.73.30.206) (Quit: hamishmack)
2016-12-07 20:40:35 +0000refold(~refold@188.172.147.158) (Remote host closed the connection)
2016-12-07 20:44:05 +0000yhhko(~tulcod@unaffiliated/tulcod)
2016-12-07 21:48:13 +0000hamishmack(~hamishmac@202-21-137-106.wlgcl1.acsdata.co.nz)
2016-12-07 22:24:02 +0000yhhko(~tulcod@unaffiliated/tulcod) (Quit: Leaving)
2016-12-07 23:32:41 +0000edsko(~quassel@23.27.206.197)
2016-12-07 23:37:33 +0000ddere(uid110888@gateway/web/irccloud.com/x-sfcufwxeybiieufe)
2016-12-07 23:40:13 +0000danpalmer(uid121480@gateway/web/irccloud.com/x-bsxbyrbutdehojgr)
2016-12-07 23:46:09 +0000edsko(~quassel@23.27.206.197) (Remote host closed the connection)
2016-12-08 00:47:25 +0000begriffs(~begriffs@104.156.228.70)
2016-12-08 01:42:49 +0000danpalmer(uid121480@gateway/web/irccloud.com/x-bsxbyrbutdehojgr) (Quit: Connection closed for inactivity)
2016-12-08 02:02:56 +0000edsko(~quassel@23.27.206.197)
2016-12-08 02:25:19 +0000hamishmack(~hamishmac@202-21-137-106.wlgcl1.acsdata.co.nz) (Read error: Connection reset by peer)
2016-12-08 02:41:19 +0000begriffs(~begriffs@104.156.228.70) (Quit: Leaving...)
2016-12-08 02:41:29 +0000refold(~refold@188.172.156.156)
2016-12-08 03:44:24 +0000hamishmack(~hamishmac@121.73.30.206)
2016-12-08 03:57:38 +0000lspitzner(~lspitzner@p4FCCD039.dip0.t-ipconnect.de) (Ping timeout: 264 seconds)
2016-12-08 03:58:30 +0000hexagoxel(~hexagoxel@p200300798F207100021E33FFFE2231E9.dip0.t-ipconnect.de) (Ping timeout: 258 seconds)
2016-12-08 03:59:58 +0000lspitzner(~lspitzner@p200300798F1D4500021E33FFFE2231E9.dip0.t-ipconnect.de)
2016-12-08 04:04:00 +0000hexagoxel(~hexagoxel@p4FCCDED9.dip0.t-ipconnect.de)
2016-12-08 04:47:02 +0000dcoutts_implements "cabal new-* all" target syntax
2016-12-08 04:47:14 +0000 <dcoutts_> e.g. cabal new-build all, new-test all etc
2016-12-08 04:47:40 +0000 <dcoutts_> hvr: adding unit-id syntax would be quite doable
2016-12-08 04:48:12 +0000 <dcoutts_> happy with "cabal new-build unitid:thelongunitidname-x8402e7a5c812... " ?
2016-12-08 04:48:21 +0000 <dcoutts_> ie unitid as a namespace qualifier
2016-12-08 04:48:44 +0000 <dcoutts_> since there does not need to be a convenient short form in that case
2016-12-08 04:51:00 +0000 <ezyang> is thelongunitidname-x8402e7a5c812 a valid component name? it is right?
2016-12-08 04:58:35 +0000 <dcoutts_> ezyang: I believe so yes
2016-12-08 04:58:59 +0000 <dcoutts_> or indeed a package name
2016-12-08 04:59:49 +0000 <dcoutts_> ezyang: so yes in principle 'unitid:thelon...' is ambigious with a package named 'unitid' containing a component 'thelon...'
2016-12-08 04:59:54 +0000 <ezyang> yeah...
2016-12-08 04:59:57 +0000 <dcoutts_> but we have way of handing that
2016-12-08 05:00:24 +0000 <dcoutts_> the strategy for all these things is ever longer and more pedantic qualification
2016-12-08 05:00:52 +0000 <ezyang> dcoutts_: I think for a machine programmable interface, it's important for the common use case to also be unambiguous in all situations