SebastianVerified account

it was/could be more useful when there was a way to change/set the HomeObject of a method. It does seem pretty weird tho, still.

Any idea who I could bug to find the rationale, or meeting notes? I’m curious to see the history since I trust there’s a good reason.

I'd wager most people didn't even consider you could do that (I know I hadn't). Was it spec'ed specifically for that, or is it a side-effect of the addition of `super` on top of some other semantic?

No idea! Fairly sure it’s specifically specced. It’s so awkward to use since changing the prototype of objects isn’t very ergonomic, and is pretty frowned upon.

are we talking about all super property references, or just in object literal methods? It potentially makes sense for some mixin uses in object methods, but idk

Just in object literal methods, I've never seen a legit use for it and seems like it complicates implementers lives

I was looking into using them for the Prepack output in some edge cases but wasn’t super useful even then. Would’ve preferred a reflective API to create functions with new home objects. I think that’s generally the case. The declarative APIs are getting harder to patch/evolve.

I have been working on AST-related tooling for literally years and I am just now learning this is a thing