Vote for block decorators!

[shrinktofit]

Use of legacy decorators can easily result in circular reference if a module import binding is passed to a decorator:

import Base from './base.mjs';
export default class Derived {
  @type(Base)
  base;
}

import Derived from './derived.mjs';
export default class Base {
  @type(Derived)
  derived;
}

since decorators are executed in module execution stage.

However, with block decorators, we could defer the getting of import bindings:

import Base from './base.mjs';
export default class Derived {
  @deferred(@type { Base }) // Equals to @deferred(() => Base)
                                              // We could get `Base` after all modules finished their execution!
  base;
}

[littledan]

Huh, I don't see how we'd make block decorators work in an expression context like that. If we want to have deferred references, maybe this kind of decorator could help: rbuckton/proposal-refs#11

[shrinktofit]

If we want to have deferred references, maybe this kind of decorator could help: rbuckton/proposal-refs#11

It does help. 👍 All I needed is just wrap the decorated expression in a function.