Well... there goes TypeScript being a superset of JavaScript. This is where the roads separate, I guess, unless TS gets a prompt update.
> we need to allow public fields with the same name.
I'd say there's no such a thing: private properties always begin with a #, while publics ones never do.
Yeah, my thoughts exactly. I don't buy the whole you need hashmarks but not a keyword argument... not to mention how we "always had" privates, but not protecteds.