TC39 Delegates
2022-05-10
plaintext logs
prev next
source on github
00:02
<Jack Works>
right, true enough. altho probably not a ton, since having a thenable module is broken in node (i forget if it's broken just in the repl, or just not in the repl)
IIRC a machine learning library uses this to emulate TLA, so they don't need to request the user to wait for the Web Assembly to be loaded
00:06
<Jack Works>
Rather than adding a symbol to the module, could we allow a user to add a built-in symbol to a function they export named then that would indicate it shouldn't be used for Promise fulfillment? Non-native promises might not understand it, but it would still work for imports.
Oh this idea is more interesting, but looks like they don't want to make promises more complex to fix this footgun
00:11
<Mathieu Hofman>
Oh this idea is more interesting, but looks like they don't want to make promises more complex to fix this footgun
Any changes will make promises more complex.
00:36
<Jack Works>
yeah of course
00:37
<Jack Works>
that's a tradeoff, some prefer fixing footgun and some prefer simplicity
00:40
<Jack Works>
https://wintercg.org/work
07:08
<Ashley Claymore>

What about:

let { _then: then } = await import(path, {
  alias: { then: _then }
});
08:39
<Rob Palmer>
Reminder: Please fill in the delegate survey to help guide the July plenary that could happen in SF. https://github.com/tc39/Reflector/issues/434
18:54
<ptomato>
does anyone know what the difference between :: and ::: in ecmarkup grammar signifies? re. https://github.com/tc39/proposal-temporal/issues/2190
18:59
<bakkot>
::: is for the grammar used for parsing strings to numbers
19:01
<bakkot>
in like +'10', I mean, not when parsing actual number literals
19:01
<bakkot>
it's never used when actually parsing source text
19:02
<bakkot>
vs, : is for translating tokens to parse nodes, :: is for translating code points to tokens (or regexes, I guess)
19:02
<ptomato>
I see! thanks
19:18
<Richard Gibson>

@bakkot is "never used when actually parsing source text" the distinction between :: and :::?

The latter is also used for the URI grammar at https://tc39.es/ecma262/multipage/global-object.html#sec-uri-syntax-and-semantics , although that grammar does not appear to participate in parsing at all and the only inbound references I see are to |uriReserved| and |uriUnescaped|, the former being a "one of" alternative of 10 static code points and the latter being an alternative of three such single-code-point nonterminals (case-insensitive ASCII letter |uriAlpha|, ASCII digit |DecimalDigit|, and no-escape-required ASCII punctuation |uriMark|).

19:20
<bakkot>
these decisions all predate my time, and the spec mostly just says what delimiters are used rather than why, in https://tc39.es/ecma262/multipage/notational-conventions.html#sec-syntactic-and-lexical-grammars
19:21
<bakkot>
but yeah, ::: is for parsings strings rather than source text seems consistent with the current usages