That is a very important clarification and I imagine TypeScript will leverage this new feature. That said, I still don't like the #. I think that will be the b

That is a very important clarification and I imagine TypeScript will leverage this new feature. That said, I still don't like the #. I think that will be the biggest issue with adoption (at least based on feedback on this post). Would the spec have to come up with another symbol if they wanted to implement `protected` behavior? Alternatively: `this.private.value`, `definitelyNotThis.value`