Bradley Farias

I would prefer this be left to the ecosystem for everything that doesn't map to property descriptor fields for now (`configurable`/`writable`/`enumerable` in particular).

@ljharb I have concerns about those and see them as non-trivial.

For: ```mjs @freeze class A {} ``` ```mjs @seal class A {} ``` Extending those classes would not allow adding properties, but does allow adding private fields. This seems something...

@mbrowne while I agree that there are cases where arrow functions are not ideal, I'm not convinced that `@bound` is always preferable to arrow functions either.

Since there is disagreement on these, I want to discuss it. I'm open to adding things as standard library features, but don't think doing so on first iteration is necessary....

I'd would prefer to leave it for a follow on. That said, I do like to `delete MyClass.constructor` somewhat often so it is tempting.

@targos added a guard

@targos after some digging, a variety of those are all from the test reporter used: https://github.com/tapjs/tap-mocha-reporter/pull/68

we have patched some stuff in the wild, we should run CITGM again

https://github.com/tapjs/tap-mocha-reporter has landed a fix, we should be good to try a new CITGM to see what the status is in the ecosystem.