TC39 General on 2022-09-28

06:17	<bakkot>	`(0, Array.of)(1); // [1] (0, Promise.resolve)(0) // throws` which of these is better, do you think
06:18	<bakkot>	keeping in mind how subclassing works - `class X extends Array {}; (0, X.of)(1)` also gives an array, not an X, unlike a direct `X.of(1)` invocation
06:19	<bakkot>	I guess it's possible to have a third kind of thing, like an autobinding getter... not sure that's better though
06:19	<bakkot>	the thing where subclasses also inherit static methods is bonkers to me
06:20	<bakkot>	(context: I would like to revive the `Set.of`/`Set.from` proposal, maybe)
06:40	<littledan>	Sounds like maybe you have some other rationale in mind in addition to the above?
06:41	<littledan>	Oh sorry revive, not remove? Well, my position is: those hazards just aren’t so bad and we shouldn’t worry about them
07:07	<yulia>	It is up to the TC, but we were doing it yearly (so it would be in december). If there are no changes to either group we do not necessarily need to hold an election
07:08	<yulia>	It is likely worthwhile to update the tc on any upcoming work, just to keep everyone informed.
12:29	<Ashley Claymore>	`(0, Array.of)(1); // [1] (0, Promise.resolve)(0) // throws` which of these is better, do you think With new methods moving away from checking Symbol.species, static methods not using `this` as the constructor seems inline with that? So if subclasses want their instances to be returned then they need to explicitly override both instance and static methods. A hassle but easier to remember perhaps
14:59	<bakkot>	Oh sorry revive, not remove? Well, my position is: those hazards just aren’t so bad and we shouldn’t worry about them which hazard are you referring to there? there's two different behaviors currently in the language and I am trying to figure out whether to go with the `Array` one or the `Promise` one
15:04	<bakkot>	Array is weird in that it's basically `let ctor = this ?? Array`, so if you do `SubclassOfArray.of(x)` you get a `SubclassOfArray` but if you do `(0, SubclassOfArray.of)(x)` you get an `Array` proper, so I guess another option is to do the simpler thing of always using the original constructor and not using `this` at all
15:10	<bakkot>	anyway I agree none of the downsides is particularly bad, I mostly just want to pick one
15:10	<bakkot>	leaning towards the Array one I guess
15:15	<Jack Works>	Oh sorry revive, not remove? Well, my position is: those hazards just aren’t so bad and we shouldn’t worry about them but which one is hazard
16:12	<Michael Ficarra>	It is up to the TC, but we were doing it yearly (so it would be in december). If there are no changes to either group we do not necessarily need to hold an election it'd still be nice to reserve time for discussion to make sure everyone is happy with how things are going with the current members
22:03	<littledan>	Oh yeah sorry I lean towards picking Array semantics or just ignoring this