Consistent getter declarations using d/lazy about d HOT 3 CLOSED

I understand confusion, still lazy should not be understood as a getter, it's about lazy initialization of a variable and it also doesn't make sense as an initialization of some getter configuration

Lazy initialization, means that on first access, given value is initialized via provided function, then it's defined directly on an instance, and for any further access it's just accessed directly (no getters involved).

Also initial descriptor that is created with d(fn) is important, as it's characteristics would be used for variable definition on an instance. If we would ask to do it via d.gs then there would be a collision, as we wouldn't be able to control setting for writable characteristics (it doesn't apply to getters)

from d.

@medikoo Right on. Thanks for the explanation.

I think for me I'll just need to use several calls to Object.defineProperties: one using lazy and the other without.

from d.

@mjackson I think the most convenient way to to define both type of properties is as follows

Object.defineProperties(Object.assign({
  regularOne: d(....),
  regularTwo: d(...)
}, lazy({
  lazyOne: d(function () { ... }),
  lazyTwo: d(function () { ... })
}));

And I understand your point, initially I wanted to make lazy so it just return descriptor, but lazy needs to know the name of the property, that's the reason it's designed to work only with name/descriptor map.

from d.