Robert Jackson

Checkout https://github.com/emberjs/ember.js/commit/ff9673f07a1ac61621be3fdb982379ec2e357848

@edeis53 - `mergedProperties` is a special property with special implementation details in Ember.Object ([see the docs for details](https://api.emberjs.com/ember/3.10/classes/EmberObject/properties/mergedProperties?anchor=mergedProperties)), if you are _not_ trying to use that feature I'd suggest using...

Thanks for writing this up @jelhan! A few of us (@wycats, @krisselden, @chancancode, @pzuraq, @dgeb, and myself) discussed this (along with other GlimmerVM / Rendering issues) last night, and we...

> That kind of feels like just adding more friction to every service definition Just to be clear, it is only required for multi-word services.

> @rwjblue waiting until 5.0 would lock us into having to provide a shim around @glimmer/tracking until then, which I would prefer not to. Ideally, @glimmer/tracking could be completely independent...

I think it is a _tad_ difficult to suggest "just use `@tracked`" at the moment, since we _also_ expect addons to continue supporting [email protected] which doesn't support tracking concepts. It...

Deprecations are added in order to be _helpful_ to folks that might be using a given API. They are definitely not something that is "required" at all for private APIs....

> The harder part might be teaching core team members and other heavily-enfranchised individuals. There is a specific tone here that I find troubling. The onus of this RFC absolutely...

The line between public and private is fairly clear: anything that is documented **must** be documented as either `@public` or `@private` (enforced by documentation linting), and anything undocumented is private....

Just to throw another example in the ring, I think we could probably make something like this work: ```hbs {{#let foo=(whatever) bar="something else" as |@bar @foo|}} {{/let}} ``` Basically allowing...