[breaking] Stop running in the next loop

[jrjohnson]

This moves back to setting the property synchronously and adds
instructions for handling errors which are caused by this. In this case
causing the error seems better than creating difficult to see timing
bugs when Run.next() is invoked.

Lots of context and discussion and fixes #203.

Context for the original change (reverted here) in #195

[jrjohnson]

@lifeart I thought I would try and save you some time by taking a pass at this as a first draft. Let me know if I'm miss-interpreting the conversation over in #203 and I can revise.

[lifeart]

@jrjohnson thank you for PR! I was thinking, glimmerjs/glimmer-vm#1061 may resolve original issue.

I was thinking about @Tracked, we can resolve property descriptor, and if descriptor has "set" method, run action in next runloop, if not - in current

[jrjohnson]

OK, shall I close this an await a glimmer solution? We can work around this in the interim by setting the values we need using {{did-insert}} manually.

[lifeart]

@jrjohnson what do you think about sync/async logic, based on property descriptor?
tldr: if property defined and has getter/setter - use async implementation, if property not defined or has "simple" descriptor - use sync implementation

[jrjohnson]

Sorry @lifeart, I don't have enough understanding of the underlying tech to comment either way, I'm happy to test it out though!

[lifeart]

@jrjohnson see https://ember-twiddle.com/aa44c20fcbc9d8b318cd45d3b8d9252d?openFiles=templates.components.my-component%5C.hbs%2Ctemplates.components.my-component%5C.hbs

[lifeart]

Since this addon counted as legacy, closing this merge request in favour of https://github.com/lifeart/ember-ref-bucket
@jrjohnson thank you for your work on it and pushing this case forward! Hope updated implementation bring more clarity and stability.