最新消息:雨落星辰是一个专注网站SEO优化、网站SEO诊断、搜索引擎研究、网络营销推广、网站策划运营及站长类的自媒体原创博客

javascript - Lazy getter doesn't work in classes - Stack Overflow

programmeradmin3浏览0评论
class a {
    get b() {
        delete this.b;
        return this.b = 1;
    }
}

var c = {
    get b() {
        delete this.b;
        return this.b = 1;
    }
}

console.log(c.b); // works as expected
console.log((new a()).b); // throws error

The above code should work fine but the last line throws.

Uncaught TypeError: Cannot set property b of # which has only a getter(…)

Clearly the getter is not being deleted in class whereas it works fine in object. I am on latest stable chrome.

Lazy Getter MDN Entry

class a {
    get b() {
        delete this.b;
        return this.b = 1;
    }
}

var c = {
    get b() {
        delete this.b;
        return this.b = 1;
    }
}

console.log(c.b); // works as expected
console.log((new a()).b); // throws error

The above code should work fine but the last line throws.

Uncaught TypeError: Cannot set property b of # which has only a getter(…)

Clearly the getter is not being deleted in class whereas it works fine in object. I am on latest stable chrome.

Lazy Getter MDN Entry

Share Improve this question asked Jun 22, 2016 at 20:45 AchsharAchshar 5,2438 gold badges42 silver badges72 bronze badges 4
  • You don't have a constructor in class a – Redu Commented Jun 22, 2016 at 20:56
  • @Redu Constructor is optional in js classes. – Achshar Commented Jun 22, 2016 at 21:00
  • I could not find a reference after a fair amount of googling, so I'm making this a comment instead of an answer -- but I am 95% certain that methods in classes end up being non-configurable, and hence, delete fails. You can mimic that behavior in "regular" classes. – Jeremy J Starcher Commented Jun 22, 2016 at 21:03
  • @JeremyJStarcher So it's by design immutable. Cool. I can accept that if you add it. – Achshar Commented Jun 22, 2016 at 21:04
Add a comment  | 

3 Answers 3

Reset to default 21

The getter of the class sits on the .prototype object, not on this, that's why your attempt to delete it fails (and, as Jeremy points out, it is not deletable).

You can however simply create an own property on the instance that shadows the getter:

class a {
    get b() {
        Object.defineProperty(this, "b", { value: 1, writable: false, configurable: true })
        return this.b;
    }
}

var c = new a;
console.log(c.b); // 1

We have to use Object.defineProperty() as a simple assignment would find the inherited property that has no setter and throws.

By design, class properties are not deletable -- reference: https://github.com/jeffmo/es-class-fields-and-static-properties

Instance Field Initialization Process

The process for executing a field initializer happens at class instantiation time. The following describes the process for initializing each class field initializer (intended to run once for each field in the order they are declared):

  • Let instance be the object being instantiated.
  • Let fieldName be the name for the current field (as stored in the slot on the constructor function).
  • Let fieldInitializerExpression be the thunked initializer expression for the current field (as stored in the slot on the constructor function).
  • Let initializerResult be the result of evaluating fieldInitializerExpression with this equal to instance.
  • Let propertyDescriptor be PropertyDescriptor{[[Value]]: initializerResult, [[Writable]]: true, [[Enumerable]]: true, [[Configurable]]: false}. Call instance.[[DefineOwnProperty]](fieldName, propertyDescriptor).

Well obviously this is about constructors. When you neglect the constructor the property you define with the getter gets created at the constructors prototype hence the correct way of doing the job probably should be like as follows;

class a {
    get b() {
        delete this.constructor.prototype.b;
        return this.constructor.prototype.b = 1;
    }
}
z = new a();
z.b; // 1
发布评论

评论列表(0)

  1. 暂无评论