[FEATURE] New CP syntax

[cibernox]

No description provided.

[cibernox]

I see that @truenorth did the very same thing. Very similar implementation too.

[stefanpenner]

I would love for you too to collaborate on this instead.

[cibernox]

What do you mean? Both collaborate on #9477 or I keep working on this as a separate idea?

[cibernox]

BTW, this is the easiest approach possible.
The internal semantics of computed remains the same, but at definition time I just build a function that decides if it should invoke the getter of the setter based on the number of parameters.

Not sure you think this is the best idea in the long term. Maybe it's more convenient to take the opposite path and change the internal behavior of computed to call the getter or the setter and when we provide a functions instead of an object we build an object with only a setter.

I think this would be more performant and would also simplify parts of the code.
By example Ember.set wouldn't need to check if a function is wrapped or check its arity.
The bad part is that this will be a breaking change. We can create a function that invokes other functions (like I just did) but we can't decompose existing functions with arity 3 into getters and setters.

We could do something like this and raise a deprecation warning if someone provides a function with arity > 1, because providing only a function means that is a getter-only CP, and eventually (2.0) refactor code to change the internals to the opposite, as I just explained.

[cibernox]

Closed in favour of #9527