Source Phase Imports for Stage 3 (cont’d from Day 1) has been added to the schedule as the final item tomorrow

littledan: it'd be great if we could ask the stenographer tomorrow to bump up their line length to as close to infinity as possible, and also to autocorrect any multiple spaces down into one, including after a period

conflicts with KKL's constraint (unavailable Thursday) and JGT's constraint (although it appears JGT constraint is satisfied if it's the 13:00-13:30 slot)

I'm reaching out to others on my team to see if someone can be present for the overflow topic this afternoon. Unfortunately, I'm giving a talk in the afternoon that couldn't be rescheduled.

Luca Casonato: guybedford --- it appears the Thursday slot at 13:00 will work, per KKL's blessing there. sound good?

I mildly prefer not to have this in the proposals table just so that there are not multiple sources of truth

Kris Kowal: we may be able to move it to Wednesday though. please hold. apologies for the disarray -- tough shuffling with constraints 🙂

Luca Casonato: guybedford --- it appears the Thursday slot at 13:00 will work, per KKL's blessing there. sound good?

nicolo-ribaudo: Would an init() change the order of the calls?

Having

init(v) {
  nextInit(v * 2)
}

would allow having the same order of function calls as set() and the same order of transforms

oh, like, per-field, we don't want a per-field initializer function

Suggestion for fuller explanation: Decompose what happens into individual Object.defineProperty() calls in the order they would execute.

ljharb: only assigning due to dynamic evaluation seems the opposite of what implementers want. IIRC, for the class to have a stable shape resulting from its declaration, then [Symbol.metadata] must be defined due to syntax, not dynamic evaluation.

true, but that means that decorated classes now will suddenly start getting a metadata object

littledan: "with fallback only on undefined" - do you mean and not null? Symbol.iterator uses undefined or null

Aren't iterators always supposed to meet the requirement that myIterator[Symbol.iterator]() === myIterator ? Doing this fallback at all seems weird to me.

why? if it hasn't touched it why would it need to close it

pattern matching is still stage 1 and i would assume it would just follow whatever is decided here

bakkot: https://github.com/search?q=language%3Ajavascript+grouptoobject&type=code

Would it be possible to add it inside iterable helpers?

Wouldn't it be Object.groupBy() since it returns an object?

i think a few of us just misspoke and said "Array.groupBy"

are we, as tc39 delegates, able to confer IPR protection by forming a TG?

littledan: Since you fit this into a shorter time slot, you could bring this back as overflow later in this meeting for TG4 creation consensus.

littledan: we will also have to assign chairs and (when we get approval for a new document) assign an editor group

If we create the TG, I think we can.

const isConstructor = (a) => { if (Object(a) !== a) { return false; } try { Promise.prototype.finally.call({ constructor: { [Symbol.species]: a }, then(){} }); } catch { return false; } return true; };

bakkot spec has been updated: https://github.com/pzuraq/ecma262/pull/10/files

are Proxies allowed?

function isConstructor(f) {
  let v = false;
  try {
    Reflect.construct(new Proxy(f, {
       construct() { v = true; }
    }), []);
  } catch() {};
  return v;
}

I love how small this specification is. It makes me feel like we got it right.

bakkot spec has been updated: https://github.com/pzuraq/ecma262/pull/10/files

I’m wondering whether decorators for derived classes are likely to continue to function if the Symbol.metadata of the base class is frozen. But more importantly, hoping there’s somewhere I can putter to find out.

Maybe we fix the overrride mistake but only for metadata objects? 😎