00:04:31  * Haragethjoined
00:23:15  * Haragethquit (Remote host closed the connection)
00:25:30  * SinisterRectusquit (Read error: Connection reset by peer)
00:31:09  * SinisterRectusjoined
00:32:11  * SinisterRectusquit (Client Quit)
00:42:35  * rendarquit (Quit: std::lower_bound + std::less_equal *works* with a vector without duplicates!)
01:21:55  * rgrinbergquit (Ping timeout: 252 seconds)
02:24:04  * Haragethjoined
02:28:34  * Haragethquit (Ping timeout: 240 seconds)
03:09:45  * rgrinbergjoined
04:05:20  * rgrinbergquit (Ping timeout: 260 seconds)
04:15:48  * Haragethjoined
04:22:05  * Haragethquit (Ping timeout: 276 seconds)
04:43:41  <rphillips>/quit
04:46:37  * rphillipsquit (Quit: ZNC - http://znc.in)
04:49:00  * rphillipsjoined
08:18:36  * Haragethjoined
08:23:23  * Haragethquit (Ping timeout: 250 seconds)
09:43:13  * rendarjoined
10:32:34  * bjornquit (Ping timeout: 260 seconds)
10:33:12  * bjornjoined
10:33:13  * bjornquit (Changing host)
10:33:13  * bjornjoined
11:20:34  * Haragethjoined
11:25:16  * Haragethquit (Ping timeout: 252 seconds)
12:02:09  * SkyRocknRoll_joined
12:09:46  * mmicko_joined
13:21:27  * Haragethjoined
13:25:43  * Haragethquit (Ping timeout: 252 seconds)
13:39:45  <daurnimator>creationix: well if you're okay with it
13:40:04  <daurnimator>konobi: well they're people working in the area so I should listen to their opinion
13:40:08  <daurnimator>konobi: what TZ are you?
13:46:17  * rgrinbergjoined
14:43:29  * cptGjoined
15:06:22  <cptG>Hello! I'm thinking about embedding luvi into an application of mine - but the libuv loop would not run on the main thread but rather in its own thread, possibly there will be more than one at a time or at several loops running in sequence. Should I expect any trouble? Does luv depend on any global state?
15:08:20  <cptG>...my rationale for this: I have already embedded luajit into my application with my own ways of embedding lua bytecode into the executable, my own loaders and whatnot. I'd like for luvi to use MY lua state instead of the other way around.
15:13:53  * SkyRocknRoll_quit (Remote host closed the connection)
15:22:18  <daurnimator>cptG: using the one lua state from multiple threads will end in tears.
15:22:49  <daurnimator>cptG: integrate luv into your existing mainloop (or vice-versa)
15:22:56  * Haragethjoined
15:24:33  <cptG>daurnimator: nope, not one lua state for multiple threads. multiple thread with its own lua state each and also (optionally) its own libuv loop, managed via luv
15:24:52  <cptG>the idea is to have a UI loop in the main loop and a luv loop in non-GUI thread(s)
15:25:53  <daurnimator>cptG: why use threads?
15:26:06  <daurnimator>cptG: (why not just do it all in the one/main thread)
15:27:49  * Haragethquit (Ping timeout: 252 seconds)
15:29:43  <cptG>there are long-running tasks that should not block the main thread. These are also not doable with async IO but still need to happen in the lua thread. In other applications, (depending on the config & use case) there are high frequency tasks that should not be blocked by the UI loop (a window resize is enough to screw with that)
15:52:24  * rgrinbergquit (Ping timeout: 276 seconds)
15:58:39  * rgrinbergjoined
16:04:40  * SinisterRectusjoined
16:12:15  * SinisterRectusquit (Read error: Connection reset by peer)
16:13:09  * SinisterRectusjoined
16:23:08  * SkyRocknRolljoined
16:53:37  * rgrinbergquit (Ping timeout: 252 seconds)
17:11:11  * rgrinbergjoined
17:18:40  * rgrinbergquit (Ping timeout: 260 seconds)
18:08:29  * rgrinbergjoined
18:09:20  <konobi>daurnimator: PST
18:09:58  <daurnimator>konobi: k. I'm about to go to sleep now (4am!)
18:10:20  <daurnimator>konobi: but if you're interested, I'd love to take you through some API design stuff with lua-http
18:14:25  <konobi>sure
18:57:18  * rgrinbergquit (Ping timeout: 244 seconds)
19:04:35  * rgrinbergjoined
19:05:17  * SkyRocknRollquit (Remote host closed the connection)
19:24:47  * Haragethjoined
19:29:40  * Haragethquit (Ping timeout: 244 seconds)
19:58:45  * rgrinbergquit (Ping timeout: 244 seconds)
20:54:30  * SinisterRectusquit (Ping timeout: 246 seconds)
21:08:31  * SinisterRectusjoined
21:45:22  * rendarquit (Ping timeout: 260 seconds)
22:15:13  * rendarjoined
22:55:44  * rendarquit (Quit: std::lower_bound + std::less_equal *works* with a vector without duplicates!)
23:26:27  * Haragethjoined
23:26:56  * rgrinbergjoined
23:31:19  * Haragethquit (Ping timeout: 260 seconds)