01:37:29  * piscisaureus_quit (Quit: ~ Trillian Astra - www.trillian.im ~)
04:35:16  * scwhjoined
08:38:25  * mmaleckijoined
08:44:37  * mmalecki_joined
08:44:58  * mmaleckiquit (Ping timeout: 245 seconds)
08:50:05  * mmaleckijoined
08:53:09  * mmalecki_quit (Ping timeout: 256 seconds)
09:01:38  * mmaleckiquit (Ping timeout: 252 seconds)
10:10:38  * scwhquit (Quit: scwh)
13:18:18  * mmaleckijoined
13:33:00  * mmalecki_joined
13:35:46  * mmaleckiquit (Ping timeout: 244 seconds)
13:39:52  * mmalecki_quit (Ping timeout: 260 seconds)
18:54:13  * scwhjoined
19:04:11  * mraleph_webjoined
19:04:42  <mraleph_web>indutny: I don't have any IRC client on me at the moment. Traveling :-)
19:04:49  <indutny>ah
19:04:51  <mraleph_web>indutny: so I'll be using web interface
19:04:52  <indutny>mraleph_web: np
19:05:13  <indutny>so basically I wanted to ask what do you think about following concept
19:05:23  <mraleph_web>indutny: so how can I help you?
19:05:26  <indutny>probably it's already widely used in that or another adaptation
19:05:50  <indutny>mraleph_web: The idea is in merging isolates
19:05:54  <indutny>some kind of thread support
19:05:58  <indutny>w/o shared data
19:06:16  <indutny>you can start thread and pass some data to it, which will be copied and inserted into some heap block
19:06:48  <indutny>that block will have special gc mark that tells that block is from external thread
19:07:10  <mraleph_web>this quickly might turn into nightmare :-)
19:07:11  <indutny>once thread(isolate) has finished - that block's mark is resetted
19:07:15  <indutny>mraleph_web: indeed
19:07:36  <indutny>but this way you can return a big amount of data from one thread to another
19:07:40  <indutny>w/o copying it
19:07:42  <mraleph_web>you can have a sticky "marked" bit for this purposes.
19:07:56  <indutny>yep
19:08:00  <indutny>so what do you think about it?
19:08:01  <mraleph_web>that would work.
19:08:13  <indutny>do you found it useful?
19:08:28  <mraleph_web>it might also cause memory leaks if used not very carefully :-)
19:08:33  <indutny>haha
19:08:36  <indutny>yep, as always
19:09:03  <mraleph_web>well effecient sharing of data between isolated threads is definitely useful.
19:09:31  <indutny>I wonder if dart is able of this thing too
19:10:36  <indutny>ok, I'll refine my idea after HIR/LIR stuff will be finished
19:10:41  <indutny>mraleph_web: thank you for listening! :)
19:11:26  <mraleph_web>I think this is what Erlang is using for their lightweight processes. They support some kind hybrid heaps that both have isolated and shared portions.
19:14:19  <indutny>hm...
19:14:27  <indutny>I'll explore this
19:14:29  <indutny>thanks
19:20:55  <indutny>mraleph_web: it seems that erlang is serializing/deserializing data when passing it back and forth between processes
19:21:09  <indutny>though I'm not really sure about this
19:22:41  <indutny>mraleph_web: http://www.erlang.org/doc/efficiency_guide/processes.html#id68101
19:24:01  <mraleph_web>ah it seems they backed this off because they could not implement it effeciently/correctly.
19:24:10  <indutny>hahaha
19:24:17  <indutny>other reading http://java-monitor.com/forum/showthread.php?t=890
19:24:26  <mraleph_web>indutny: http://stackoverflow.com/a/3406586
19:25:13  <indutny>indeed
19:25:48  <indutny>but my article claims another thing
19:26:01  <indutny>The message heap is a heap for data that is used in messages. Messages too are shared between processes. Messages are passed between threads by copying a pointer over from the sending thread to the receiving thread. The data for the message is stored on the message heap.
19:27:20  <indutny>though it's 2008 article
19:29:24  <indutny>mraleph_web: well, initially I thought not about sharing data, but about returning values on thread's finish to parent thread
19:35:54  <indutny>mraleph_web: ok, time to sleep
19:35:55  <indutny>ttyl
19:36:55  * mraleph_webquit (Ping timeout: 245 seconds)
19:54:09  * hij1nxjoined
21:28:08  * mmaleckijoined
21:30:33  * mmalecki_joined
21:33:28  * mmalecki_quit (Client Quit)
21:33:46  * mmalecki_joined
21:33:52  * mmaleckiquit (Ping timeout: 250 seconds)
21:33:58  * mmalecki_quit (Client Quit)
21:34:11  * mmaleckijoined
21:41:47  * mmalecki_joined
21:44:32  * mmaleckiquit (Ping timeout: 245 seconds)
21:48:12  * mmalecki_quit (Ping timeout: 248 seconds)
21:53:03  * scwhquit (Quit: scwh)
21:59:27  * mmaleckijoined
22:29:30  * mmaleckiquit (Quit: leaving)