Ron Buckton

@typescript-bot perf test

This PR is currently on hold. The main use cases for this feature require a fair amount of complexity that is likely to run any implementation against the recursion depth...

> At some point this flag should probably be aliased/renamed to `legacyDecorators` or something, since “experimental” tends to imply “bleeding edge” and I can imagine future people unfamiliar with TS’s...

> 1. Why Non-static members currently have no way to access the constructor or prototype during class definition? That is the current behavior of the proposal, but an alternative is...

Private static elements should now be supported as of the latest commit.

> @rbuckton Hey, I'm looking forward to this landing, any idea when that might happen? I imagine once this PR merges, the next nightly might have this? Yes, it should...

I'm thinking of pulling the `--annotateTransforms` diagnostics switch into its own PR and instead emitting the annotations as some type of source map extension. That plus a VS Code extension...

> I'm thinking of pulling the `--annotateTransforms` diagnostics switch into its own PR ... This is done, the `--annotateTransforms` diagnostics switch has been moved to #51307 instead.

> The following has a pretty opaque error message and I'm not sure why it's implemented incorrectly. > ```ts > function fieldIdentity( > target: object, > context: ClassFieldDecoratorContext > ):...

> The following has a pretty opaque error message and I'm not sure why it's implemented incorrectly. @DanielRosenwasser: I made a few changes in b5a2ad6 to ensure a more useful...