-
Notifications
You must be signed in to change notification settings - Fork 18
Path to Stage 4! #12
Comments
Closes tc39#605, relates to tc39#567 / tc39/proposal-global#12 / bocoup@9c45e2a
Closes #605, relates to #567 / tc39/proposal-global#12 / bocoup@9c45e2a
- Adds intrinsic `%GlobalThisValue%` - Sets it in `SetRealmGlobalObject` - Adds global name `global` Per tc39/proposal-global#12
- Adds intrinsic `%GlobalThisValue%` - Sets it in `SetRealmGlobalObject` - Adds global name `global` Per tc39/proposal-global#12
- Adds intrinsic `%GlobalThisValue%` - Sets it in `SetRealmGlobalObject` - Adds global name `global` Per tc39/proposal-global#12
Chrome started implementing |
Thanks; i'm subscribed and it's already linked in the OP :-) |
- Adds intrinsic `%GlobalThisValue%` - Sets it in `SetRealmGlobalObject` - Adds global name `globalThis` Per tc39/proposal-global#12
- Adds intrinsic `%GlobalThisValue%` - Sets it in `SetRealmGlobalObject` - Adds global name `globalThis` Per tc39/proposal-global#12
Sorry that I am catching this a bit late, but I am wondering about the wording of this PR, which was set in this commit in response to this thread. I am wondering, how did you arrive at this wording, rather than using the wording in @domenic's suggestion? |
Which PR are you referring to? |
Is there anything you could say about why you went towards this wording rather than the wording Domenic suggested? I can't find information about it in commit messages or bug threads. |
Nope, I’m afraid i can’t remember my reasons from 2 years ago. I believe it seemed like the most minimal modification to the existing text. Since Domenic hasn’t brought it up, do you have a preference for an alternative? |
I have a preference for the wording Domenic suggested, all else being equal. It seems unnecessary to me to create another separate name for the global this value, when we already have another way of referring to it. |
I’m worried about this part: #17 (comment) |
|
@Jack-Works It isn't by default. You probably have enabled the "Experimental JavaScript" flag. |
@targos oh yes I forgot it |
It's in Chrome 71 (beta):
|
It's implemented in SpiderMonkey |
In case you want to update the OP: |
Thanks :-) the OP already notes this. |
@ljharb It doesn’t currently note that it shipped behind a flag in Chrome 70. |
ah true, thanks, updating now |
- Adds intrinsic `%GlobalThisValue%` - Sets it in `SetRealmGlobalObject` - Adds global name `globalThis` Per tc39/proposal-global#12
- Adds intrinsic `%GlobalThisValue%` - Sets it in `SetRealmGlobalObject` - Adds global name `globalThis` Per tc39/proposal-global#12
- Adds intrinsic `%GlobalThisValue%` - Sets it in `SetRealmGlobalObject` - Adds global name `globalThis` Per tc39/proposal-global#12
- Adds intrinsic `%GlobalThisValue%` - Sets it in `SetRealmGlobalObject` - Adds global name `globalThis` Per tc39/proposal-global#12
@ljharb Will you be bringing this proposal before the committee for stage 4 at the next meeting? |
Quite possibly, as soon as i have the stomach for further internet outrage. |
- Adds intrinsic `%GlobalThisValue%` - Sets it in `SetRealmGlobalObject` - Adds global name `globalThis` Per tc39/proposal-global#12
- Adds intrinsic `%GlobalThisValue%` - Sets it in `SetRealmGlobalObject` - Adds global name `globalThis` Per tc39/proposal-global#12
Stage 4
Stage 3Stage 2The text was updated successfully, but these errors were encountered: