00:02:25  <bterlson>tschneidereit: no argument there
00:03:07  <bterlson>except minor perf wins I imagine
00:04:46  <aklein>This is one of the oldest V8 bugs: https://bugs.chromium.org/p/v8/issues/detail?id=90
02:34:45  * bdnuggerquit (Quit: Connection closed for inactivity)
02:41:18  * gibson042joined
02:45:09  * AtumT_quit (Remote host closed the connection)
02:59:19  * jwaldenquit (Quit: ChatZilla 0.9.92-rdmsoft [XULRunner 35.0.1/20150122214805])
03:12:00  * Draggorquit (Read error: No route to host)
03:20:27  * floatleftquit (Ping timeout: 240 seconds)
03:21:58  * not-an-aardvarkjoined
03:24:17  * floatleftjoined
03:27:59  <Domenic>I don't see any way to lock down sort completely without specifying exactly what comparison algorithm everyone must use
03:28:05  <Domenic>Which seems probably bad?
03:38:05  * Draggorjoined
04:01:10  <ljharb>that seems like exactly the struggle; everyone wants to maximally lock down `sort`, and everyone also doesn't want to mandate a sorting algorithm :-/
04:01:16  <ljharb>also some people want stable sorts
04:01:32  * gibson042quit (Ping timeout: 255 seconds)
04:42:44  * caridyquit (Remote host closed the connection)
05:18:23  * gcommerquit (Remote host closed the connection)
05:25:13  * jmdyckquit (Remote host closed the connection)
05:25:52  * gcommerjoined
05:33:39  * MisterAJjoined
06:12:19  * MisterAJquit (Quit: Page closed)
07:22:01  * floatleftquit (Read error: Connection reset by peer)
07:24:02  * floatleftjoined
10:55:05  <annevk>What is the problem with locking down the sorting algorithm? It's bound to be somewhat inflexible at this point anyway due to web compat
10:57:31  <annevk>Although reading the backlog it seems Edge does fun stuff and maybe gets away with it...
11:25:10  * mylesborinsquit (Quit: farewell for now)
11:25:41  * mylesborinsjoined
11:41:59  * AtumTjoined
12:41:38  * not-an-aardvarkquit (Quit: Connection closed for inactivity)
13:04:22  * jmdyckjoined
13:13:37  * Wizekjoined
13:31:26  * bradleymeckjoined
13:40:15  * bradleymeckquit (Quit: bradleymeck)
14:11:55  * gibson042joined
14:39:23  * AtumT_joined
14:42:33  * AtumTquit (Ping timeout: 265 seconds)
15:06:29  * caridyjoined
15:18:10  * bradleymeckjoined
15:23:14  * Fishrock123joined
16:00:08  * floatleftquit (Ping timeout: 240 seconds)
17:07:03  * caridyquit (Remote host closed the connection)
17:07:38  * caridyjoined
17:42:23  * basicdaysquit (Ping timeout: 250 seconds)
17:50:28  <caitp>v8 isn't "unstable", it's "unstable if there are > some number (25?) elements"
17:50:53  <caitp>which I think is also done in other engines
17:51:04  <caitp>probably with different stable/unstable thresholds
18:25:56  * AtumTjoined
18:28:34  * AtumT_quit (Ping timeout: 255 seconds)
18:33:34  * jwaldenjoined
18:44:52  * caridyquit (Read error: Connection reset by peer)
18:45:52  * jwaldenquit (Quit: back shortlyish)
18:46:44  * caridyjoined
19:17:07  * not-an-aardvarkjoined
19:17:13  * basicdaysjoined
19:34:30  * jwaldenjoined
19:34:32  * jwaldenquit (Client Quit)
19:34:50  * jwaldenjoined
19:42:37  * jwaldenquit (Remote host closed the connection)
19:45:04  * jwaldenjoined
20:19:40  * jwaldenquit (Quit: back later sometime, or tomorrow at worst)
22:15:07  * Fishrock123quit (Remote host closed the connection)
22:45:35  * caridyquit (Read error: Connection reset by peer)
22:46:07  * caridyjoined
22:57:59  * Fishrock123joined
23:46:31  * AtumTquit (Remote host closed the connection)
23:48:40  * bradleymeckquit (Quit: bradleymeck)
23:57:37  * bradleymeckjoined
23:58:18  * bradleymeckquit (Client Quit)