00:14:31  * AtumTquit (Remote host closed the connection)
02:52:52  * xaxxonjoined
05:14:09  * xaxxonquit (Ping timeout: 264 seconds)
05:35:17  * xaxxonjoined
05:54:35  * xaxxonquit (Ping timeout: 255 seconds)
05:55:12  * xaxxonjoined
06:17:46  * plutoniixjoined
07:07:53  * plutoniixquit (Quit: Leaving)
07:17:09  * xaxxonquit (Ping timeout: 260 seconds)
07:28:52  * xaxxonjoined
09:20:00  * xaxxonquit (Ping timeout: 248 seconds)
09:20:07  * xaxxon_joined
09:21:13  * xaxxon_changed nick to xaxxon
11:09:01  * xaxxonquit (Quit: xaxxon)
11:25:11  * mylesborinsquit (Quit: farewell for now)
11:25:41  * mylesborinsjoined
12:37:03  * AtumTjoined
14:51:04  * bradleymeckjoined
15:12:54  * bradleymeckquit (Read error: Connection reset by peer)
15:13:12  * bradleymeckjoined
15:22:10  * cloudshujoined
15:27:52  * bradleymeckquit (Read error: Connection reset by peer)
15:28:04  * bradleymeckjoined
16:00:30  * AtumT_joined
16:03:39  * AtumTquit (Ping timeout: 256 seconds)
16:13:50  * AtumTjoined
16:14:45  * AtumT_quit (Ping timeout: 264 seconds)
16:38:16  * RT|Chatzillaquit (Quit: ChatZilla 0.9.86.1 [Firefox 2.0.0.22pre/2010030309])
17:25:38  * bradleymeckquit (Quit: bradleymeck)
17:39:35  * bradleymeckjoined
17:44:10  * seventhjoined
19:44:45  * seventhquit (Remote host closed the connection)
22:22:15  <bradleymeck>is there a sane way to iterate over an object using Symbol.iterator in C++?
22:28:44  <caitp>bradleymeck: that would be pretty cool
22:29:05  <caitp>I mean, you could write your own wrapper to do that
22:29:17  <caitp>I don't think there's an API for it yet, though
22:36:27  <bradleymeck>caitp: I'm not entirely sure how much speed gain I would get out of it
22:37:02  <caitp>it would very likely be slow
22:37:03  <bradleymeck>also, is there any chance Private might become available cross Isolate
22:37:19  <bradleymeck>caitp: I'm iterating over what is likely a crap ton of object wrappers
22:37:37  <caitp>in the API, we could make it fast for builtin iterators if the prototype chain isn't modified, like we try to do at the JS level
22:37:50  <caitp>you'd have trouble doing that in your own wrapper though :(
22:38:02  <bradleymeck>haha, I can push it out to JS for now
22:38:11  <bradleymeck>but I'm starting to get to weird APIs
22:38:25  <bradleymeck>like returning a Private to JS...
22:38:39  <bradleymeck>which I'm pretty sure is frowned upon
22:38:51  <caitp>I don't actually know anything about Private, let me look at it real quick
22:39:14  <bradleymeck>caitp: it looks like a special Symbol, but nothing else seems really clear
22:39:51  <caitp>yeah, so you generally wouldn't want to leak that to JS
22:40:24  <bradleymeck>caitp: it isn't to userland JS ;p just for node internals
22:40:27  <caitp>they're basically just property names that you can stick on things unobservably, but if you leak them, it potentially becomes observable
22:40:32  <bradleymeck>but still probably a frowny face
22:41:11  <caitp>well I mean, they're used in v8 internally all the time, historically were used even more
22:41:36  <caitp>I think gsathya is using them for class private fields, even
22:45:28  <bradleymeck>good enough for me, kind wish we had a membrane to see if something is leaked to userland
22:49:13  * RT|Chatzillajoined
23:10:44  * bradleymeckquit (Quit: bradleymeck)
23:23:04  * bradleymeckjoined
23:27:55  * bradleymeckquit (Client Quit)
23:43:39  * plutoniixjoined