@v8js v7.4, Chrome 74, and Node.js v12 support both public and private class fields!
https://developers.google.com/web/updates/2018/12/class-fields …pic.twitter.com/6ee404KKnv
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Hmm, that sounds unnecessarily confusing IMHO. @littledan @bakkoting might have more context.
No worries, at least I pointed to an existing language spec and working implementation rather than just an argument. :)
I appreciate the background!
That was brought up a few times; see this question and the subsequent one in the FAQ (depending on whether you think `o.priv` should access the private field of that name only when `o` has it or all of the time):https://github.com/tc39/proposal-class-fields/blob/master/PRIVATE_SYNTAX_FAQ.md#why-not-do-a-runtime-check-on-the-type-of-the-receiver-to-determine-whether-to-access-the-private-or-public-field-named-x …
Yeah, we wanted to make sure that, if you used the same name on a different property of a different object, it didn't suddenly break when using that object inside a class.
Did that break in AS3?
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.