Prepare to implement tracked storage, RFC#669 #20761
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation here is that I want to stop folks from using https://github.com/ember-polyfills/ember-tracked-storage-polyfill (and swap its implementation to use the real implementation (here, hopefully)
This doesn't make sense to continue work on until
lands -- because I don't really want to continue the fake-glimmer packages we have in
@ember/-internals/metal
Additionally, this RFC, https://rfcs.emberjs.com/id/0669-tracked-storage-primitive#re-implementing-tracked-with-storage, kinda just likes like Starbeam concepts, so it should be super easy:
ez