00:34:07  * Left_Turnjoined
00:49:26  * Wraithanquit (Ping timeout: 272 seconds)
00:50:48  * Wraithanjoined
00:52:34  * bnoordhuisjoined
00:56:46  * chrisdickinsonquit (Ping timeout: 240 seconds)
00:56:56  * bnoordhuisquit (Ping timeout: 250 seconds)
01:01:16  * rendarquit (Quit: std::lower_bound + std::less_equal *works* with a vector without duplicates!)
01:01:26  * chrisdickinsonjoined
01:04:00  * terinjokesquit (Ping timeout: 272 seconds)
01:04:55  * terinjokesjoined
01:23:13  * Fishrock123quit (Quit: Leaving...)
01:48:35  * brsonquit (Quit: leaving)
02:13:14  * dap_quit (Quit: Leaving.)
02:23:43  * ruyi_du_joined
02:26:38  * ruyi_du__quit (Ping timeout: 250 seconds)
02:36:28  * ruyi_du_quit (Read error: Connection reset by peer)
02:36:54  * ruyi_du_joined
02:52:32  * ncthom91joined
03:00:24  * jgiquit (Quit: jgi)
03:07:19  * brsonjoined
03:19:05  * tunniclmquit (Ping timeout: 276 seconds)
03:21:41  * happy-dudequit (Ping timeout: 260 seconds)
03:24:10  * happy-dudejoined
03:29:29  * fierydrake__quit (Ping timeout: 276 seconds)
03:51:42  * ncthom91quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
04:14:23  * s3shsjoined
04:28:35  * brsonquit (Quit: leaving)
05:07:10  * a3fjoined
05:16:52  * rmgquit (Remote host closed the connection)
05:17:26  * rmgjoined
05:22:07  * rmgquit (Ping timeout: 265 seconds)
05:27:28  * a3fquit (Quit: Zzzzz..)
05:46:27  * s3shsquit (Quit: Computer has gone to sleep.)
06:14:00  * Ruyijoined
06:19:46  * Ruyiquit (Quit: Good bye)
06:49:06  * bradleymeckjoined
06:51:58  * |jemc|quit (Quit: WeeChat 1.3)
08:14:10  * [spoiler]joined
08:14:55  * amurzeau_joined
08:47:20  * evanlucasquit (Read error: Connection reset by peer)
08:47:58  * evanlucasjoined
08:50:43  * bradleymeckquit (Read error: Connection reset by peer)
08:51:45  * bnoordhuisjoined
08:55:02  * bradleymeckjoined
09:03:47  <[spoiler]>If I am understanding this right, libuv's `uv_queue_work` adds work to be done by the threadpool, right? Are some threads reserved for libuvs's internal gimmicks, or not? (I'm asking because, if I'll have to be careful with scheduling some long-running task since the threadpool also does disk IO).
09:08:23  <ruyi_du_>i have the same question :)
09:11:41  <[spoiler]>ruyi_du_: I skimmed the source and it seems we'll have to be careful :P
09:14:42  <ruyi_du_>thankyou, long-running task maybe need to create thread
09:15:30  <ruyi_du_>threadpool have four thread in default configuration
09:18:26  * bnoordhuisquit (Ping timeout: 245 seconds)
09:18:49  * rendarjoined
09:18:50  <[spoiler]>ruyi_du_: indeed, but you can increase it with an environment variable
09:20:42  <ruyi_du_>yup
09:22:04  <[spoiler]>ruyi_du_: yeah it's possible to just create a one-off thread or managing your own threadpool shouldn't be an issue
09:28:39  <ruyi_du_>run in a thread from the threadpool, said in documention
09:29:19  <ruyi_du_>this point should be explain clearly, right?
09:39:46  * happy-dudequit (Quit: Connection closed for inactivity)
09:44:42  * brrtjoined
09:57:07  * tunniclmjoined
10:07:22  * brrtquit (Quit: brrt)
10:11:26  * ruyi_du_quit (Read error: Connection reset by peer)
10:18:06  <[spoiler]>Oh no I understood that it does that, but I assumed it wouldn't delegate it to a thread if less than `n-reserved` free, but then there'd need to be some bookkeeping required which might just make uv bloaty, I guess
10:21:10  <[spoiler]>and that's probably not the desired behaviour anyway
10:21:12  <amurzeau_>this might be related: https://github.com/libuv/libuv/issues/660
10:23:01  * tomgcojoined
10:23:57  <amurzeau_>and the enhancement proposal: https://github.com/libuv/leps/pull/4
10:25:23  * bnoordhuisjoined
10:29:40  * bnoordhuisquit (Ping timeout: 245 seconds)
10:41:31  <[spoiler]>amurzeau_: oh thanks for the links! I saw that proposal few years back
10:43:10  * rmgjoined
10:47:53  * rmgquit (Ping timeout: 265 seconds)
10:50:49  * seishunjoined
10:54:04  * a3fjoined
10:56:34  * brrtjoined
11:18:25  * brrtquit (Quit: brrt)
11:44:34  * etnbrdquit (Ping timeout: 244 seconds)
12:15:13  * bnoordhuisjoined
12:17:22  * davijoined
12:17:23  * daviquit (Changing host)
12:17:23  * davijoined
12:32:55  * brrtjoined
12:34:05  * brrtquit (Client Quit)
12:35:07  * zju4joined
12:37:17  * zju1quit (Ping timeout: 250 seconds)
12:37:17  * zju3quit (Ping timeout: 250 seconds)
12:37:36  * zju3joined
12:49:48  * bradleymeckquit (Read error: Connection reset by peer)
13:16:42  * bnoordhuisquit (Ping timeout: 250 seconds)
13:37:52  * bradleymeckjoined
13:42:26  * bradleymeckquit (Ping timeout: 240 seconds)
13:44:40  * rmgjoined
13:45:34  * tunniclmquit (Read error: Connection reset by peer)
13:45:57  * tunniclmjoined
13:49:37  * rmgquit (Ping timeout: 265 seconds)
13:52:27  * happy-dudejoined
14:06:06  * daviquit (Ping timeout: 250 seconds)
14:57:05  * s3shsjoined
15:10:02  * bnoordhuisjoined
15:26:20  * bnoordhuisquit (Ping timeout: 245 seconds)
15:37:10  * alexforsterjoined
15:41:27  * Fishrock123joined
15:43:50  * mmickoquit (Ping timeout: 245 seconds)
16:03:13  <nathan7>trevnorris: For me, the unsafeAlloc makes a bunch of sense
16:03:38  <nathan7>trevnorris: In, say, Rust, I write `unsafe { … }` to do things the compiler can't prove correct
16:04:08  <nathan7>trevnorris: It doesn't mean it's *dangerous*, it means that a mistake in that code may cause it to violate expectations other parts of the system have
16:04:37  <nathan7>trevnorris: `unsafe { … }` is "hold my beer, compiler, I know what I'm doing" — and what you and I are most likely to use when it's useful
16:08:08  <nathan7>trevnorris: If my code is doing something funny, by producing undefined values / displaying undefined behaviour, I'll grep for unsafe
16:08:17  <nathan7>trevnorris: and double-check that code
16:14:34  * bnoordhuisjoined
16:14:47  * rmgjoined
16:17:03  * bnoordhuisquit (Read error: Connection reset by peer)
16:38:57  * davijoined
16:55:42  * Wraithanpart ("WeeChat 0.4.2")
17:11:29  * jgijoined
17:15:29  * fierydrake__joined
17:23:46  * brsonjoined
18:21:22  * dap_joined
18:22:16  * jgiquit (Quit: jgi)
18:28:31  * jgijoined
18:38:53  * s3shsquit (Quit: Computer has gone to sleep.)
18:41:00  * daviquit (Ping timeout: 260 seconds)
18:58:55  * tunniclmquit (Ping timeout: 240 seconds)
19:01:26  * fierydrake__quit (Ping timeout: 256 seconds)
19:04:31  * fierydrake__joined
19:20:42  * fierydrake__quit (Ping timeout: 256 seconds)
19:25:33  * s3shsjoined
19:56:28  * mmaleckiquit (Ping timeout: 265 seconds)
20:17:27  * zju3quit (Remote host closed the connection)
20:37:19  * amurzeaujoined
20:47:04  * s3shsquit (Quit: Computer has gone to sleep.)
20:53:38  * davijoined
20:53:39  * daviquit (Changing host)
20:53:39  * davijoined
21:02:59  * s3shsjoined
21:03:06  * fierydrake__joined
21:04:26  * tunniclmjoined
21:05:53  * jgiquit (Quit: jgi)
21:19:26  * tunniclmquit (Ping timeout: 250 seconds)
21:19:29  * s3shsquit (Quit: Computer has gone to sleep.)
21:21:54  * rendarquit (Ping timeout: 272 seconds)
21:27:43  * rendarjoined
21:31:21  * alexforsterquit (Quit: Textual IRC Client: www.textualapp.com)
21:47:41  * s3shsjoined
22:10:34  * daviquit (Ping timeout: 250 seconds)
22:12:40  * jgijoined
22:17:05  * s3shsquit (Quit: Computer has gone to sleep.)
22:18:37  * mmaleckijoined
22:24:36  * s3shsjoined
22:36:12  * zju3joined
22:43:03  * zju1joined
22:46:02  * seishunquit (Ping timeout: 250 seconds)
22:46:24  * zju4quit (Ping timeout: 256 seconds)
22:54:00  * a3fquit (Quit: bb)
23:15:18  * s3shsquit (Quit: Computer has gone to sleep.)
23:19:59  * Fishrock123quit (Quit: Leaving...)
23:23:05  * s3shsjoined
23:38:33  * s3shsquit (Quit: Computer has gone to sleep.)
23:39:23  * dap_quit (Quit: Leaving.)
23:48:03  * bradleymeckjoined
23:57:46  * mmaleckiquit (Ping timeout: 240 seconds)