03:21
<Jack Works>
it's really hard to educate people why JavaScript class works this way
03:21
<Jack Works>
other class features don't have this problem when inheriting
03:22
<Jack Works>
if we use the accessor semantics for class fields, it will also be good with inherit
05:13
<bakkot>
I feel like "fields are on the instance, methods are on the prototype" is pretty straightforward?
07:35
<nicolo-ribaudo>
Are the two explicit resource management proposals going to be merged back, now that they are both at stage 3? rbuckton
12:50
<littledan>
I feel like "fields are on the instance, methods are on the prototype" is pretty straightforward?
We definitely could have done accessors for fields. It would have certain advantages and disadvantages. I am also very confident that, if we did that, people would have said “this has lots of footguns, look this basic code doesn’t work as expected”
19:57
<rbuckton>
Are the two explicit resource management proposals going to be merged back, now that they are both at stage 3? rbuckton
Yes, see https://github.com/tc39/proposal-explicit-resource-management/pull/154
19:58
<rbuckton>
I'm just waiting for reviews from waldemar and shu
20:20
<nicolo-ribaudo>
Thank you!