| 04:59 | <bakkot> | sure, you just need to remove the <emu-meta effects="user-code"> in the GetBindingValue definition for module environment records. note that sending any PR, even trivial ones, currently requires signing https://tc39.es/agreements/contributor/ |
| 05:00 | <bakkot> | the repo is https://github.com/tc39/ecma262 |
| 05:02 | <bakkot> | I don't understand the question, sorry. what do you mean by "what is this for"? It's for... informing the reader that getting undefined here implies that Receiver does not currently have a property P. |
| 05:02 | <bakkot> | all asserts are for informing the reader of something which it is helpful to know and is not necessarily obvious from the immediate context |
| 21:22 | <Francisco Tolmasky> | Is there a term for "non-callable objects" (in other words, objects that don't have anything in the [[Call]] slot, and thus return "object" from typeof)? I don't see anything in the ECMAScript spec that gives such objects a definitive name (such as "plain object" or "non-callable object" etc) |
| 21:24 | <Francisco Tolmasky> | I see "ordinary object", "exotic object", "standard object", and "built-in object", all of which could be callable or non-callable |
| 21:30 | <jmdyck> | I'm pretty sure there isn't such a term. You might say "an object that isn't a function [object]", but I don't think the spec even does that. |
| 21:34 | <Francisco Tolmasky> | unfortunate |