Cleanup enumerable
Merge pull request #5541 from knownasilya/uniq

Cleanup enumerable mixin
More ES3 fixes.

Still need to conditionally switch on browsers that do not have ES5 compliant accessors, because isEnabled is compiled out based on development vs production build.
Merge pull request #5535 from krisselden/mandatory-setter-es3-fix

Fix for ES3 browsers in development mode.
[DOC] Small grammar fix on enumerable filter method
Merge pull request #5545 from shama/typo

[DOC] Small grammar fix on enumerable filter method
[DOC release] fixed spelling error in dag.js docs
Merge pull request #5551 from davidpett/patch-1

[DOC release] fixed spelling error in dag.js docs
Multiline
Merge pull request #5554 from twokul/multiline

Multiline
Update ember-cli to 0.0.44.
Merge pull request #5561 from rwjblue/update-ember-cli

Update ember-cli to 0.0.44.
Make _view a special prefix instead of a keyword
Merge pull request #5574 from mmun/view-prefix

Make _view a special prefix instead of a keyword
Pass depKey and old/new value to will/didChange

Until now, when a property is set, we were passing to [did|will]Change
only the object and the name of the property.
This information is very limited for some uses.
I can be very handy by example to know inside didChange the old value of
the property.
Similarly, it can also be useful to know the new value inside willChange
When the didChange is triggered by changes in a dependency, we might also
need to know which dependency changed.

All this information was available in the `set` method, so now those
values are propagated all the way thought `iterDeps` until did/will change.

The info of the change is also pased for array dependencies.
In this kind of changes, the only information I have is the numbed of values
added, but not the actual elements being added.