2014-03-04 13:45:17 +0000ircbrowse(~chrisdone@unaffiliated/chrisdone)
2014-03-04 14:05:41 +0000 <ircbrowse> http://ircbrowse.net/browse/haskell-distributed :-)
2014-03-04 14:07:15 +0000 <hyperthunk> Cool, we have IRC logs now. Thanks Christopher Done!
2014-03-04 14:35:46 +0000nkpart(uid3844@gateway/web/irccloud.com/x-yprgvtusngediker) (Quit: Connection closed for inactivity)
2014-03-04 14:38:39 +0000hyperthunk(~hyperthun@host86-181-42-247.range86-181.btcentralplus.com) (Quit: hyperthunk)
2014-03-04 14:48:57 +0000hyperthunk(~hyperthun@46.233.116.206)
2014-03-04 15:19:25 +0000alanz(~alanz@105-237-77-168.access.mtnbusiness.co.za)
2014-03-04 16:12:18 +0000hyperthunk(~hyperthun@46.233.116.206) (Quit: hyperthunk)
2014-03-04 16:12:57 +0000hyperthunk(~hyperthun@46.233.116.206)
2014-03-04 16:28:25 +0000hyperthunk(~hyperthun@46.233.116.206) (Quit: hyperthunk)
2014-03-04 16:44:54 +0000hyperthunk(~hyperthun@host86-181-42-247.range86-181.btcentralplus.com)
2014-03-04 17:29:47 +0000edsko(~edsko@80.111.60.101) (Quit: This computer has gone to sleep)
2014-03-04 18:16:29 +0000edsko(~edsko@80.111.60.101)
2014-03-04 18:18:40 +0000hyperthunk(~hyperthun@host86-181-42-247.range86-181.btcentralplus.com) (Quit: hyperthunk)
2014-03-04 19:09:24 +0000edsko(~edsko@80.111.60.101) (Quit: This computer has gone to sleep)
2014-03-04 19:22:28 +0000hyperthunk(~hyperthun@host86-181-42-247.range86-181.btcentralplus.com)
2014-03-04 19:54:52 +0000hyperthunk(~hyperthun@host86-181-42-247.range86-181.btcentralplus.com) (Quit: hyperthunk)
2014-03-04 20:34:36 +0000hyperthunk(~hyperthun@host86-181-42-247.range86-181.btcentralplus.com)
2014-03-04 21:10:21 +0000asmyers(~quassel@128.177.88.167) (Ping timeout: 244 seconds)
2014-03-04 21:26:41 +0000travis-ci(~travis-ci@ec2-54-204-209-158.compute-1.amazonaws.com)
2014-03-04 21:26:41 +0000travis-ci- [travis-ci] haskell-distributed/distributed-process#55 (development - 5861abc : Tim Watson): The build is still failing.
2014-03-04 21:26:41 +0000travis-ci- [travis-ci] Change view : https://github.com/haskell-distributed/distributed-process/compare/484b2cd8d22c...5861abc216e7
2014-03-04 21:26:41 +0000travis-ci- [travis-ci] Build details : http://travis-ci.org/haskell-distributed/distributed-process/builds/20086587
2014-03-04 21:26:41 +0000travis-ci(~travis-ci@ec2-54-204-209-158.compute-1.amazonaws.com) ()
2014-03-04 21:27:41 +0000hyperthunkneeds to get around to updated all the CH projects to use the working travis-ci config we've got for d-p-platform
2014-03-04 21:30:07 +0000hyperthunk(~hyperthun@host86-181-42-247.range86-181.btcentralplus.com) (Quit: hyperthunk)
2014-03-04 21:51:31 +0000lukexi(~lukexi@c-67-188-105-141.hsd1.ca.comcast.net)
2014-03-04 21:54:40 +0000alanz(~alanz@105-237-77-168.access.mtnbusiness.co.za) (Quit: Ex-Chat)
2014-03-04 22:31:06 +0000hyperthunk(~hyperthun@host86-181-42-247.range86-181.btcentralplus.com)
2014-03-04 22:57:13 +0000nkpart(uid3844@gateway/web/irccloud.com/x-voznhgnfqnygvstn)
2014-03-04 23:12:23 +0000lukexi(~lukexi@c-67-188-105-141.hsd1.ca.comcast.net) (Quit: lukexi)
2014-03-04 23:16:58 +0000 <carter> hyperthunk: one of the big things i hope to fix is making unsafeSend safe
2014-03-04 23:17:07 +0000carter(carter@2600:3c03::f03c:91ff:fe6e:6c01) (Quit: ZNC - http://znc.in)
2014-03-04 23:17:31 +0000carter(carter@2600:3c03::f03c:91ff:fe6e:6c01)
2014-03-04 23:17:38 +0000 <hyperthunk> carter: explain?
2014-03-04 23:17:42 +0000 <hyperthunk> explain*
2014-03-04 23:17:48 +0000 <hyperthunk> can't spell tonight, or type for that matter
2014-03-04 23:18:14 +0000hyperthunkarm, or read for that matter. :/
2014-03-04 23:18:30 +0000 <hyperthunk> so carter - unsafeSend
2014-03-04 23:18:47 +0000 <hyperthunk> it's only unsafe because we don't guarantee that the data being passed is fully evaluated
2014-03-04 23:19:04 +0000 <hyperthunk> if you use the 'send' variant in d-p-platform then that *is* safe
2014-03-04 23:19:06 +0000 <hyperthunk> mainly
2014-03-04 23:19:18 +0000 <hyperthunk> because it enforces NFData on the term being sent
2014-03-04 23:19:43 +0000 <hyperthunk> the only reason it matters (that we enforce that) is we do not serialise those calls, since they're just moving data around the local node using STM
2014-03-04 23:19:56 +0000 <hyperthunk> once you get into remote calls, it's all irrelevant anyway
2014-03-04 23:19:58 +0000 <hyperthunk> plus……
2014-03-04 23:20:15 +0000 <carter> soke
2014-03-04 23:20:16 +0000 <carter> ok
2014-03-04 23:20:17 +0000 <carter> currently unsafe send is "trust me, its ok"
2014-03-04 23:20:18 +0000 <carter> what you really want is "this is only allowed for local shared heap messages"
2014-03-04 23:20:18 +0000 <hyperthunk> it would be ***much*** more useful for someone to actually help figure out why serialisation is so slow
2014-03-04 23:20:20 +0000 <carter> this goes back to that data families thing i mentioned
2014-03-04 23:20:22 +0000 <carter> can you gureantee its only used for shared heap?
2014-03-04 23:20:27 +0000 <carter> hows that gurantee you're only sending to shared heap addresses ?
2014-03-04 23:20:28 +0000 <carter> i know
2014-03-04 23:20:29 +0000 <carter> :t send
2014-03-04 23:20:30 +0000 <carter> i agree
2014-03-04 23:20:32 +0000 <carter> what i'm saying
2014-03-04 23:20:33 +0000 <carter> is how does this get enforced
2014-03-04 23:20:34 +0000 <carter> that you're only using unsafe send on local messages
2014-03-04 23:20:42 +0000 <hyperthunk> carter: it does
2014-03-04 23:20:54 +0000 <hyperthunk> if you use unsafeSend to a remote pid, it just ends up going to safe send
2014-03-04 23:20:56 +0000 <hyperthunk> :)
2014-03-04 23:21:08 +0000 <hyperthunk> it's not really "unsafe"
2014-03-04 23:21:27 +0000 <hyperthunk> it's just risky for the case where (a) the call *is* local and (b) there are unevaluated thunks in the message
2014-03-04 23:21:37 +0000 <carter> you're not answering my question
2014-03-04 23:21:43 +0000 <carter> :)
2014-03-04 23:21:46 +0000 <hyperthunk> carter: hahaha
2014-03-04 23:21:47 +0000 <hyperthunk> sorry
2014-03-04 23:21:48 +0000 <hyperthunk> :)
2014-03-04 23:21:53 +0000 <hyperthunk> what is the question?
2014-03-04 23:22:17 +0000 <carter> how do you syntactically ensure i can only send unserialized values on a shared heap channell
2014-03-04 23:22:27 +0000 <hyperthunk> carter: I see
2014-03-04 23:22:33 +0000 <hyperthunk> that is sorta useful
2014-03-04 23:22:35 +0000 <carter> yes
2014-03-04 23:22:47 +0000 <carter> this is a key key piece of my experimental design i hope to finish up
2014-03-04 23:22:51 +0000 <hyperthunk> but really, it pales in comparison IMHO to being able to serialise and send fast over the wire
2014-03-04 23:22:53 +0000 <carter> i want to *reason*
2014-03-04 23:22:56 +0000 <hyperthunk> which currently, we're very slow at
2014-03-04 23:22:57 +0000 <carter> about when that is so
2014-03-04 23:23:02 +0000 <hyperthunk> carter: sue
2014-03-04 23:23:04 +0000 <hyperthunk> sure*
2014-03-04 23:23:05 +0000 <carter> well
2014-03-04 23:23:10 +0000 <carter> user builder
2014-03-04 23:23:13 +0000 <carter> *use builder
2014-03-04 23:23:16 +0000 <hyperthunk> but right now, your cluster is going to suck because remote messaging isn't fast enough
2014-03-04 23:23:17 +0000 <carter> for anything you're serializing
2014-03-04 23:23:19 +0000 <carter> well
2014-03-04 23:23:20 +0000 <carter> thats ok
2014-03-04 23:23:23 +0000 <carter> i've plans for that too
2014-03-04 23:23:24 +0000 <carter> :)
2014-03-04 23:23:26 +0000 <hyperthunk> carter: great - how? wanna do a pull request?
2014-03-04 23:23:33 +0000 <hyperthunk> that'd be wicked, if it's faster
2014-03-04 23:23:33 +0000 <carter> once its done
2014-03-04 23:23:46 +0000 <hyperthunk> also, we've got a 200% binary overhead in the format we use
2014-03-04 23:23:47 +0000 <hyperthunk> urgh
2014-03-04 23:23:47 +0000 <carter> i'm stilling just writing down the plans
2014-03-04 23:24:10 +0000 <hyperthunk> carter: I can take a PR that makes things faster without any discussion, as long as the tests still pass.
2014-03-04 23:24:10 +0000 <carter> I will share things once they work :)
2014-03-04 23:24:16 +0000 <hyperthunk> carter: cool, that'd be good.