What do you think? Is -> better than .# ?https://twitter.com/_gsathya/status/973231075320266752 …
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
Yes, that was another reason; thanks for the additional context. In general, I don't like making decisions just from a single "killer" example but rather looking at a bunch factors together. These can both be considerations without one being "the" reason.
Indeed. I didn't mean to imply that this was the one explanation, but rather that this is the one that caused me personally to agree to decouple it :) Of course the other concern is serious too.
I really wanted the shorthand, and will probably take another pass at arguing for it some day, but people were really weirded out by it, and I really want the feature so shorthand is on ice!
So sorry to see this feature move backward https://github.com/tc39/proposal-private-methods … And all because it worked slightly differently than some people assumed? :(
The shorthand feature was removed when we advanced to stage 3. I compromised because: 1. There was a plausible alternative semantics presented 2. It wasn't foreclosed in the future Wasn't worth holding the whole feature back.
Please tell me this doesn't actually have any chance of killing off instance fields, private state, and decorators, and moving everything back to the starting line???https://github.com/zenparsing/js-classes-1.1 …
i second @AdamRackis‘ concerns. :( please don’t let it be true.
I found the arguments for “why not fields” a bit vague and a somewhat presumptuous, I read: “this will solve previous flaws and complexities” Its hard to believe that this proposal wont suffer from equally problematic ergonomics and semantic nuances, but whatever we can learn...
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.