00:58:30  * AtumTquit (Quit: AtumT)
01:17:25  <devsnek>from a language design perspective, what if loops over iterators broke after handling a done result instead of before
01:18:05  <devsnek>is there a precedent for `{ value: undefined, done: true }`
02:16:25  * keith_mi_joined
02:23:44  * keith_mi_quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
03:08:14  * keith_mi_joined
03:09:39  * keith_mi_quit (Client Quit)
03:14:12  * keith_mi_joined
03:43:38  * gkatsevjoined
03:43:47  * gkatsevquit (Client Quit)
03:47:47  * gkatsevjoined
03:58:40  * cybaiquit (Remote host closed the connection)
03:59:17  * cybaijoined
04:04:13  * cybaiquit (Ping timeout: 276 seconds)
04:04:15  <ljharb>devsnek: not sure what you mean, that's typically the last iteration result for most iterators
04:10:43  <devsnek>ljharb: yeah but loops don't eval their bodies for it
04:11:00  <devsnek>i guess it makes sense to allow things that finish undefined
04:11:13  <devsnek>the end might not be associated with a value
04:11:19  <devsnek>just awkward interface i guess
04:12:58  <ljharb>i'm still not sure what you're getting at
04:13:13  <ljharb>do you mean like, if you eval a for..of loop, what's the completion value?
04:13:19  <devsnek>no i'm talking about iteration
04:13:32  <devsnek>its kind of awkward that `{ value: something, done: true }` is possible
04:13:45  <ljharb>isn't that only when a generator returns something?
04:13:45  <devsnek>but i am guessing the intention is that you aren't supposed to have `done: true` with some actual value
04:13:57  <devsnek>i think so
04:14:02  <devsnek>its just kind of awkward
04:14:04  <ljharb>certainly in all user code i've seen, it never checks `.value` unless `.done` is false
04:14:10  <devsnek>yeah
04:14:30  <devsnek>(for context, i'm trying to figure out the design of iteration in slither)
04:18:21  * jmdyckquit (Remote host closed the connection)
04:22:06  * gibson042quit (Quit: Leaving.)
04:46:24  * cybaijoined
05:14:37  * keith_mi_quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
05:24:17  * keith_mi_joined
08:29:44  * mgoljoined
08:30:49  * cybaiquit (Remote host closed the connection)
08:35:42  * mgolquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
08:59:35  * mgoljoined
09:09:02  * cybaijoined
09:52:34  * keith_mi_quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
09:56:37  * keith_mi_joined
10:22:56  * Havvyquit (Ping timeout: 245 seconds)
10:23:47  * Havvyjoined
10:24:06  * keith_mi_quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
10:49:00  * keith_mi_joined
11:04:11  * ArashPTquit (Ping timeout: 245 seconds)
11:13:19  * ArashPTjoined
12:12:37  * jmdyckjoined
12:17:04  * keith_mi_quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
13:24:50  * gibson042joined
14:34:53  * keith_mi_joined
14:36:04  * keith_mi_quit (Client Quit)
14:42:16  <caitp>it wouldn't be too difficult to do it
14:42:34  <caitp>oh dang, znc was scrolled way up, did I just reply to something from the distant past?
14:42:44  <caitp>this irc client, man ._.
14:48:04  <devsnek>caitp: that depends on what you were replying to
14:49:03  <caitp>it was about making `/* /* */ */` end the comment at the last `*/` instead of the first one
14:49:47  <caitp>"wouldn't be hard to do it, but what other language does that? and whats the point?"
14:54:55  <devsnek>rust does that
14:55:12  <devsnek>makes commenting a large section without worrying about the contents less annoying
14:56:38  <jmdyck>https://stackoverflow.com/questions/20528010/what-is-the-usage-of-nested-comments-in-some-programming-languages
14:57:05  <jmdyck>xquery has nested comments
14:59:41  <caitp>I think the only time when my internal dialogue is saying "wouldn't it be great if js had internal comments" is when commenting out big chunks of long unit tests to try to isolate exactly where something goes wrong --- and to work around it I just use the text editor's tools
14:59:58  <caitp>s/internal/nested/
15:21:49  * keith_mi_joined
15:22:18  * keith_mi_quit (Client Quit)
15:35:46  * cloudshujoined
16:03:07  * gibson042quit (Ping timeout: 246 seconds)
16:30:47  <rkirsling>one easy workaround is not using /* */ for anything other than a header comment 😎
16:45:04  <devsnek>rkirsling: are you suggesting `// //` for nested multiline
16:46:50  <rkirsling>devsnek: oh no I just mean that if you only use `//` amidst code then you wouldn't have to worry about whether temporarily wrapping a section in `/* */` is going to work
16:48:16  <rkirsling>(although code editors would generally insert `//` for you anyway but yeah)
16:50:29  <rkirsling>having said that, I suppose it's kind of unreasonable if JSDoc expects multiline comments
17:01:55  * ArashPTquit (Read error: Connection reset by peer)
17:03:04  * ArashPTjoined
17:24:36  * ArashPTquit (Ping timeout: 250 seconds)
17:39:05  * keith_mi_joined
17:50:49  * keith_m__joined
17:51:25  * keith____joined
17:52:04  * keith_mi_quit (Remote host closed the connection)
17:55:07  * keith_m__quit (Ping timeout: 246 seconds)
18:33:18  <caitp>proposal: C preprocessor for JS
18:33:34  <caitp>solve this problem once and for all with #if false ... #endif
18:37:11  <TabAtkins>Yeah, nestable block comments require you to actually do some level of parsing on the stuff inside the comment. Would be good anyway, as right now, you can validly write a string like `"foo*/bar"`, and then when you try to put that in a comment block, the block will end partway thru the string...
18:37:41  <rkirsling>oh dear
18:38:47  <TabAtkins>On the other hand, comment hacks like being able to toggle between two sections by doing `/**/ section one /*/ section two /**/`, and adding or removing the final slash on the first comment, are also widespread, so "fixing" comments now would break a lot of pages, I'd wager.
18:39:59  <TabAtkins>(A variant can also be used to make toggling a single section a 1-char change, rather than 2-chars twice, by putting a `/**/` before and after the section; again, removing the last slash from the first comment will comment out the whole block.)
18:40:32  * keith____quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
18:41:19  <rkirsling>hmm you're right there could be a decent amount of that in prod code
18:41:43  <caitp>yeah, it's technically very easy to solve the problem, but I wouldn't be surprised if there were compat problems with it (which I think was mentioned when this came up before)
18:44:02  <devsnek>`'use nested multiline comments'`
18:49:25  <Bakkot>I am absbolutely certain there would be webcompat problems
18:51:08  <devsnek>`'*/use/*nested*/multiline/*comments*/'`
18:57:22  * AtumTjoined
19:03:48  * Nimelrian_joined
19:20:58  * keith_mi_joined
19:52:31  * jwaldenjoined
20:29:37  * keith_mi_quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
21:31:39  * Nimelrian_quit (Ping timeout: 250 seconds)
22:49:48  * ArashPTjoined
23:10:42  * keith_mi_joined
23:40:19  * AtumTquit (Quit: AtumT)