Skip to content

Commit

Permalink
Updates
Browse files Browse the repository at this point in the history
  • Loading branch information
NullVoxPopuli committed Jan 18, 2025
1 parent 1665941 commit 5082c39
Showing 1 changed file with 4 additions and 3 deletions.
7 changes: 4 additions & 3 deletions text/1070-default-globals-for-strict-mode.md
Original file line number Diff line number Diff line change
Expand Up @@ -361,16 +361,17 @@ TC39:
- [`Array`](https://tc39.es/ecma262/#sec-constructor-properties-of-the-global-object-array)
[Example](https://limber.glimdown.com/edit?c=DwFwpgtgDgNghuAfAKAATtQb0wYjHAYwAtUAKAcxgHsAjOGAFSIEsBnAOgEEAnbuAT1QBGVACZUAZgCUqOK1QAfZuAgKAvmrQZt2ZZA1b02APT5iB4MZWwEYFEA&format=gjs)
> [!NOTE]
> This is the same behavior as `(array)` in loose mode, and `import { array } from '@ember/helper';`, however, while the creation of the array is reactive (e.g.: if we had said `(Array @foo @bar)`, changes to `@foo` and `@bar` would cause the creation of a new array instance), the proposed _built-in_ `(array)` _keyword_ behavior _may_ have reactive items, as proposed by [RFC#1068](https://github.com/emberjs/rfcs/pull/1068)
```gjs
<template>
{{#each (Array 1 2 3) as |item|}}
{{item}}
{{/each}}
</template>
```
> [!NOTE]
> This is the same behavior as `(array)` in loose mode, and `import { array } from '@ember/helper';`, however, while the creation of the array is reactive (e.g.: if we had said `(Array @foo @bar)`, changes to `@foo` and `@bar` would cause the creation of a new array instance), the proposed _built-in_ `(array)` _keyword_ behavior _may_ have reactive items, as proposed by [RFC#1068](https://github.com/emberjs/rfcs/pull/1068)
- [`BigInt`](https://tc39.es/ecma262/#sec-constructor-properties-of-the-global-object-bigint)
- [`Boolean`](https://tc39.es/ecma262/#sec-constructor-properties-of-the-global-object-boolean)
Expand Down

0 comments on commit 5082c39

Please sign in to comment.