Thanks for working on this @pzuraq.

I like that this RFC allows apps that currently use some observers to incrementally move away from them while incrementally moving to the Octane programming model at the same time.

Am I correct in saying that this RFC will allow addons like ember-composable-helpers migrate away from detecting argument changes using synchronous observers to using arguments which are tracked properties? And specifically, should it then be possible for helpers like sort-by to detect the type of arguments received and only use observers when the inputs are not tracked properties?

I would take it a step further actually, I believe helpers like sort-by will be able to convert and remove observers even if the properties they are passed are normal CPs or properties updated using set, since autotracking works with those too 😄 helpers and computed properties like Ember's own sortBy helper or the ones included in ember-macro-helpers should be able to update too. I believe the majority of, in not all, cases where sync observers are absolutely necessary can be solved with autotracking.

Pleasure reading this RFC! Would you mind explaining autotracking @pzuraq? Any links to some code I can look at to explain? I look to help updating some of these packages in the future.

I think the best explanation for the moment is in the Tracked Properties RFC. At some point I want to do a bit of a deeper dive in a blog post, but it's going to take a while to write, so I'm unsure when I'll get around to it. Hopefully sooner rather than later!

The "Rendered" link needs updating as it's pointing to https://github.com/emberjs/rfcs/blob/async-observers/text/0000-async-observers.md but the 0000 here needs to be 0494.

We discussed this in todays core team meeting, and are 👍 on moving into final comment period.

FYI - Updated the rendered link above.