Support ES2022 class-private-fields-in syntax

[cool-little-fish]

FIX #1067

[marijnh]

Any particular reason you decided to put this in parseExprAtom instead of special-casing it in parseExprOp? At a glance, it seems like this makes it easy for unsyntactic private fields to 'escape' the check in buildBinary (I believe the current code will accept class extends #foo, for example).

[cool-little-fish]

Thanks for reminding,you are right, I will modify current implementation according to your advice.

[cool-little-fish]

already updated the implementation

[marijnh]

That addresses my concern, thanks. Merged.

[mkubilayk]

It's great to see that this is already implemented in Acorn. Thanks!

Is there any chance we can get this feature released soon @marijnh? We'd greatly appreciate that. I believe it'll also unblock some ESLint work linked above.

[marijnh]

Tagged 8.6.0 with this patch.

[mkubilayk]

Thanks a lot!