Joe Pea

Ok the PR is updated (basically no change) but the question remains: how exactly do we name these two types of initializers so that it is clear which initializers we're...

Maybe the bigger problem is that people want different orderings, and having one ordering is limiting. This thread, - https://github.com/tc39/proposal-decorators/issues/465 ideates different types of initializers, and perhaps also having control...

If someone has an existing pre-decorator-era API like this: ```ls class SomeClass { a = 1 b = 2 get sum() { return this.a + this.b } constructor() { makeSignal(this,...

Someone might reply and say that the expectation is the getter/setter is always ready before fields. You have a point. But I still would rather be in control. I'd be...

It's all written on paper. Anything is possible. Remember, `Object.observe` was completely canceled from Stage 3 even after runtime implementations.

> The ordering of class evaluation is shipped in all browsers and literally can't ever be changed. I agree that can't be changed, but as pointed out in - https://github.com/tc39/proposal-decorators/issues/567...

@justinfagnani Given pre-existing JavaScript APIs that already exist for modifying objects, if decorators ran in order, it would be dead simple to make things work in various scenarios without needing...

> Decorators **do** run in order: @miyaokamarina Only partially. Your example is too simple and not using all the types of class members. In my comment right before yours, I...

> If you have multiple examples where an issue is supposedly causing problems, they should be listed in the same issue. @justinfagnani Yeah each of my issues described a differing...

> Think about whether it's furthering your own goals to fragment the conversation. It maybe isn't. Thank you sensei. 🙏 :D