From a776cc540acb15aa84020de37f8ec8a840396ac0 Mon Sep 17 00:00:00 2001
From: kategengler <kategengler@users.noreply.github.com>
Date: Fri, 21 Mar 2025 18:22:49 +0000
Subject: [PATCH 1/4] Advance RFC 1068 to Stage ready-for-release

---
 text/1068-tracked-collections.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/text/1068-tracked-collections.md b/text/1068-tracked-collections.md
index 1aaae9259e..31996b4a96 100644
--- a/text/1068-tracked-collections.md
+++ b/text/1068-tracked-collections.md
@@ -1,16 +1,16 @@
 ---
-stage: accepted
+stage: ready-for-release
 start-date: 2025-01-12T00:00:00.000Z
-release-date: # In format YYYY-MM-DDT00:00:00.000Z
+release-date:
 release-versions:
-teams: # delete teams that aren't relevant
+teams:
   - data
   - framework
   - learning
 prs:
-  accepted: https://github.com/emberjs/rfcs/pull/1068 
+  accepted: 'https://github.com/emberjs/rfcs/pull/1068'
 project-link:
-suite: 
+suite:
 ---
 
 <!--- 

From f5f172f228b36d36c2fd745ee3c992ee77c7dbd2 Mon Sep 17 00:00:00 2001
From: "Ember.js RFCS CI" <ember-rfcs@example.com>
Date: Fri, 21 Mar 2025 18:22:53 +0000
Subject: [PATCH 2/4] Update RFC 1068 ready-for-release PR URL

---
 text/1068-tracked-collections.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/text/1068-tracked-collections.md b/text/1068-tracked-collections.md
index 31996b4a96..e7e5ccf035 100644
--- a/text/1068-tracked-collections.md
+++ b/text/1068-tracked-collections.md
@@ -9,6 +9,7 @@ teams:
   - learning
 prs:
   accepted: 'https://github.com/emberjs/rfcs/pull/1068'
+  ready-for-release: 'https://github.com/emberjs/rfcs/pull/1088'
 project-link:
 suite:
 ---

From 9a55e8c8846cbe60bc12392e4bcfd6ffd25279ae Mon Sep 17 00:00:00 2001
From: NullVoxPopuli <199018+NullVoxPopuli@users.noreply.github.com>
Date: Sun, 17 Aug 2025 13:32:20 -0400
Subject: [PATCH 3/4] rfc-1068 - Update the collections to be under the
 /collections path

---
 text/1068-tracked-collections.md | 37 +++++++++++++++++++++++---------
 1 file changed, 27 insertions(+), 10 deletions(-)

diff --git a/text/1068-tracked-collections.md b/text/1068-tracked-collections.md
index e7e5ccf035..b2e0fef299 100644
--- a/text/1068-tracked-collections.md
+++ b/text/1068-tracked-collections.md
@@ -119,7 +119,7 @@ import {
     trackedObject, trackedArray, 
     trackedMap, trackedWeakMap,
     trackedSet, trackedWeakSet
-} from '@ember/reactive';
+} from '@ember/reactive/collections';
 ```
 
 ### `trackedObject`, `trackedArray`, `trackedMap`, etc
@@ -150,7 +150,7 @@ Some examples assuming implementation of [RFC#998: Make fn built-in in strict-mo
 
 
 ```gjs
-import { trackedArray } from '@ember/reactive';
+import { trackedArray } from '@ember/reactive/collections';
 
 const nonTrackedArray = [1, 2, 3];
 const addTo = (arr) => arr.push(Math.random());
@@ -188,7 +188,7 @@ const addTo = (arr) => arr.push(Math.random());
 #### Example `trackedObject`
 
 ```gjs
-import { trackedObject } from '@ember/reactive';
+import { trackedObject } from '@ember/reactive/collections';
 
 const nonTrackedObject = { a: 1 };
 const addTo = (obj) => obj[Math.random()] = Math.random();
@@ -249,6 +249,23 @@ For example, other future exports from `@ember/reactive` (in future RFCs), may i
 without the static analysis guarantees of `type=module`, every consumer of `@ember/reactive` would always have all of these exports in their build.
 For some utilities, we can place them under sub-path-exports, such as `@ember/reactive/window`, for window-specific reactive properties, but the exact specifics of each of these can be hashed out in their individual RFCs.
 
+#### Why are the collections under `@ember/reactive/collections`?
+
+ Placing the collections in the main export surface alongside core primitives like `tracked`, `cached`, `cell`, and `resource` may not conflate importance of the collections. 
+
+> [!NOTE]
+> At the time of writing of this RFC, `tracked`, `cached`, `cell`, and `resource` RFCs have not been accepted for inclusion in `@ember/reactive`
+
+This is motivated by actual usage out in the ecosystem of tracked-built-ins:
+
+here are results from github.com searches for the `tracked-built-ins` equivelents:
+- "new TrackedObject(" - [888 Results](https://github.com/search?q=%22new+TrackedObject%28%22&type=code)
+- "new TrackedArray(" - [468 Results](https://github.com/search?q=%22new+TrackedArray(%22&type=code)
+- "new TrackedSet(" - [129 Results](https://github.com/search?q=%22new+TrackedSet(%22&type=code)
+- "new TrackedWeakSet(" - [29 Results](https://github.com/search?q=%22new+TrackedWeakSet(%22&type=code)
+- "new TrackedWeakMap(" - [32 Results](https://github.com/search?q=%22new+TrackedWeakMap(%22&type=code)
+
+Additionally, specifying collections gives us a blessed path for exported other useful datastructures in the future without continually adding to the main export file (even though dead-code-elimination would eliminate what is unused - not importing what may not be used could help local development)
 
 ### Consumption
 
@@ -275,7 +292,7 @@ A utility for creating tracked arrays, copying the original data so that mutatio
 See [MDN for more information](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array)
 
 ```gjs
-import { trackedArray } from '@ember/reactive';
+import { trackedArray } from '@ember/reactive/collections';
 import { on } from '@ember/modifier';
 import { fn } from '@ember/helper';
 
@@ -302,7 +319,7 @@ A utility for creating tracked objects, copying the original data so that mutati
 See [MDN for more information](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object)
 
 ```gjs
-import { trackedObject } from '@ember/reactive';
+import { trackedObject } from '@ember/reactive/collections';
 import { on } from '@ember/modifier';
 import { fn } from '@ember/helper';
 
@@ -329,7 +346,7 @@ A utility for creating tracked maps, copying the original data so that mutations
 See [MDN for more information](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map)
 
 ```gjs
-import { trackedMap } from '@ember/reactive';
+import { trackedMap } from '@ember/reactive/collections';
 import { on } from '@ember/modifier';
 import { fn } from '@ember/helper';
 
@@ -357,7 +374,7 @@ A utility for creating tracked weak maps, copying the original data so that muta
 See [MDN for more information](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakMap)
 
 ```gjs
-import { trackedWeakMap } from '@ember/reactive';
+import { trackedWeakMap } from '@ember/reactive/collections';
 import { on } from '@ember/modifier';
 import { fn } from '@ember/helper';
 
@@ -381,7 +398,7 @@ A utility for creating tracked maps, copying the original data so that mutations
 See [MDN for more information](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Set)
 
 ```gjs
-import { trackedSet } from '@ember/reactive';
+import { trackedSet } from '@ember/reactive/collections';
 import { on } from '@ember/modifier';
 import { fn } from '@ember/helper';
 
@@ -409,7 +426,7 @@ A utility for creating tracked weak sets, copying the original data so that muta
 See [MDN for more information](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakSet)
 
 ```gjs
-import { trackedWeakSet } from '@ember/reactive';
+import { trackedWeakSet } from '@ember/reactive/collections';
 import { on } from '@ember/modifier';
 import { fn } from '@ember/helper';
 
@@ -470,7 +487,7 @@ We should do a codemod to convert the newable constructors from tracked-built-in
 Using Vite or Webpack (Embroider 3+), we can alias `tracked-built-ins` to point at the new modules, using a shim -- for example:
 ```js 
 // app/built-ins-shim.js
-import { trackedArray } from '@ember/reactive';
+import { trackedArray } from '@ember/reactive/collections';
 
 export class TrackedArray {
     constructor(arr) {

From a82818c66508362d7bbb895c6d3e53b0a76673f0 Mon Sep 17 00:00:00 2001
From: NullVoxPopuli <199018+NullVoxPopuli@users.noreply.github.com>
Date: Sun, 17 Aug 2025 14:19:20 -0400
Subject: [PATCH 4/4] Update 1068-tracked-collections.md

---
 text/1068-tracked-collections.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/text/1068-tracked-collections.md b/text/1068-tracked-collections.md
index b2e0fef299..f251f19044 100644
--- a/text/1068-tracked-collections.md
+++ b/text/1068-tracked-collections.md
@@ -258,12 +258,12 @@ For some utilities, we can place them under sub-path-exports, such as `@ember/re
 
 This is motivated by actual usage out in the ecosystem of tracked-built-ins:
 
-here are results from github.com searches for the `tracked-built-ins` equivelents:
-- "new TrackedObject(" - [888 Results](https://github.com/search?q=%22new+TrackedObject%28%22&type=code)
-- "new TrackedArray(" - [468 Results](https://github.com/search?q=%22new+TrackedArray(%22&type=code)
-- "new TrackedSet(" - [129 Results](https://github.com/search?q=%22new+TrackedSet(%22&type=code)
-- "new TrackedWeakSet(" - [29 Results](https://github.com/search?q=%22new+TrackedWeakSet(%22&type=code)
-- "new TrackedWeakMap(" - [32 Results](https://github.com/search?q=%22new+TrackedWeakMap(%22&type=code)
+here are results from github.com searches for the `tracked-built-ins` equivalents (excluding ember-owned repos and forks of them):
+- "new TrackedObject(" - [520 Results]([https://github.com/search?q=%22new+TrackedObject%28%22&type=code](https://github.com/search?q=%22new+TrackedObject%28%22+NOT+is%3Afork++NOT+org%3Aemberjs+NOT+org%3Atracked-tools+NOT+org%3Aember-cli+NOT+org%3Aember-migration-utils+NOT+org%3Aember-learn&type=code))
+- "new TrackedArray(" - [312 Results](https://github.com/search?q=%22new+TrackedArray%28%22+NOT+is%3Afork++NOT+org%3Aemberjs+NOT+org%3Atracked-tools+NOT+org%3Aember-cli+NOT+org%3Aember-migration-utils+NOT+org%3Aember-learn+&type=code)
+- "new TrackedSet(" - [74 Results](https://github.com/search?q=%22new+TrackedSet%28%22+NOT+is%3Afork++NOT+org%3Aemberjs+NOT+org%3Atracked-tools+NOT+org%3Aember-cli+NOT+org%3Aember-migration-utils+NOT+org%3Aember-learn+&type=code)
+- "new TrackedWeakSet(" - [5 Results](https://github.com/search?q=%22new+TrackedWeakSet%28%22+NOT+is%3Afork++NOT+org%3Aemberjs+NOT+org%3Atracked-tools+NOT+org%3Aember-cli+NOT+org%3Aember-migration-utils+NOT+org%3Aember-learn+&type=code)
+- "new TrackedWeakMap(" - [4 Results](https://github.com/search?q=%22new+TrackedWeakMap%28%22+NOT+is%3Afork++NOT+org%3Aemberjs+NOT+org%3Atracked-tools+NOT+org%3Aember-cli+NOT+org%3Aember-migration-utils+NOT+org%3Aember-learn+&type=code)
 
 Additionally, specifying collections gives us a blessed path for exported other useful datastructures in the future without continually adding to the main export file (even though dead-code-elimination would eliminate what is unused - not importing what may not be used could help local development)