| 00:18 | <ptomato> | is there generally accepted JS jargon for what I've been calling "user code calls"? that is, when some innocuous-looking JS code that doesn't obviously call a function, does actually call a function that may be defined somewhere else in the code (like +value may end up calling value[Symbol.toPrimitive](), etc.) |
| 00:48 | <Jack Works> | I don't know. I call it "trigger user code" |
| 01:07 | <shu> | yeah i think it's that or "can call user code" is what the spec's u mode says |
| 01:19 | <ptomato> | I think it's confusing who the "user" actually is |
| 03:18 | <Jack Works> | when we work as a framework/spec/library/engine developer, the user actually means other developer but using this term is strange I agree |
| 18:28 | <shu> | "user code" is code not under your control, so it's relative |
| 18:29 | <shu> | i don't think it's confusing in practice, since the frame of reference is usually pretty clear, whether it's a spec or a framework |