cacheFor returns the wrong value for aliased properties

Aliased properties (computed.alias, computed.readOnly, etc) return the CONSUMED object when you try to get their cached value.

ember-twiddle

export default Ember.Controller.extend({
  appName: 'Ember Twiddle',
  aliased: Ember.computed.alias('appName'),
  
  init() {
    this._super(...arguments);
    console.log('before:', this.cacheFor('aliased'));
    console.log('get:', this.get('aliased'));
    console.log('after:', this.cacheFor('aliased'));
  }
});

Expected output:

before: undefined
get: Ember Twiddle
after: Ember Twiddle

Actual output:

before: undefined
get: Ember Twiddle
after: Object {}

[dwickern]

Does public API ever distinguish between computed properties and aliases? They’re both created by Ember.computed. I assumed aliases are a special-case implementation for performance, but they should outwardly behave the same as computed properties

[locks]

@lolmaus according to https://github.com/emberjs/ember.js/issues/15545#issuecomment-317861212 it is working as expected and the issue is a misalignment of expectations. I mean that changing the behaviour of the API this late into the game can bring unexpected surprises.