Skip to content
By using Twitter’s services you agree to our Cookies Use. We and our partners operate globally and use cookies, including for analytics, personalisation, and ads.
  • Home Home Home, current page.
  • About

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @
  • Language: English
    • Bahasa Indonesia
    • Bahasa Melayu
    • Català
    • Čeština
    • Dansk
    • Deutsch
    • English UK
    • Español
    • Filipino
    • Français
    • Hrvatski
    • Italiano
    • Magyar
    • Nederlands
    • Norsk
    • Polski
    • Português
    • Română
    • Slovenčina
    • Suomi
    • Svenska
    • Tiếng Việt
    • Türkçe
    • Ελληνικά
    • Български език
    • Русский
    • Српски
    • Українська мова
    • עִבְרִית
    • العربية
    • فارسی
    • मराठी
    • हिन्दी
    • বাংলা
    • ગુજરાતી
    • தமிழ்
    • ಕನ್ನಡ
    • ภาษาไทย
    • 한국어
    • 日本語
    • 简体中文
    • 繁體中文
  • Have an account? Log in
    Have an account?
    · Forgot password?

    New to Twitter?
    Sign up
wycats's profile
Yehuda Katz 🥨
Yehuda Katz 🥨
Yehuda Katz  🥨
Verified account
@wycats

Tweets

Yehuda Katz  🥨Verified account

@wycats

Tilde Co-Founder, OSS enthusiast and world traveler.

Portland, OR
yehudakatz.com
Joined August 2007

Tweets

  • © 2018 Twitter
  • About
  • Help Center
  • Terms
  • Privacy policy
  • Cookies
  • Ads info
Dismiss
Previous
Next

Go to a person's profile

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @

Promote this Tweet

Block

  • Tweet with a location

    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

    Your lists

    Create a new list


    Under 100 characters, optional

    Privacy

    Copy link to Tweet

    Embed this Tweet

    Embed this Video

    Add this Tweet to your website by copying the code below. Learn more

    Add this video to your website by copying the code below. Learn more

    Hmm, there was a problem reaching the server.

    By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.

    Preview

    Why you're seeing this ad

    Log in to Twitter

    · Forgot password?
    Don't have an account? Sign up »

    Sign up for Twitter

    Not on Twitter? Sign up, tune into the things you care about, and get updates as they happen.

    Sign up
    Have an account? Log in »

    Two-way (sending and receiving) short codes:

    Country Code For customers of
    United States 40404 (any)
    Canada 21212 (any)
    United Kingdom 86444 Vodafone, Orange, 3, O2
    Brazil 40404 Nextel, TIM
    Haiti 40404 Digicel, Voila
    Ireland 51210 Vodafone, O2
    India 53000 Bharti Airtel, Videocon, Reliance
    Indonesia 89887 AXIS, 3, Telkomsel, Indosat, XL Axiata
    Italy 4880804 Wind
    3424486444 Vodafone
    » See SMS short codes for other countries

    Confirmation

     

    Welcome home!

    This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.

    Tweets not working for you?

    Hover over the profile pic and click the Following button to unfollow any account.

    Say a lot with a little

    When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.

    Spread the word

    The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.

    Join the conversation

    Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.

    Learn the latest

    Get instant insight into what people are talking about now.

    Get more of what you love

    Follow more accounts to get instant updates about topics you care about.

    Find what's happening

    See the latest conversations about any topic instantly.

    Never miss a Moment

    Catch up instantly on the best stories happening as they unfold.

    1. Yehuda Katz  🥨‏Verified account @wycats Jan 13
      Replying to @spion @lucasazzola and

      That issue would have been fixed by making semis mandatory in classes, which is perhaps what we should have done.

      1 reply 0 retweets 2 likes
    2. Gorgi Kosev‏ @spion Jan 13
      Replying to @wycats @lucasazzola and

      Perhaps TC39 should make that a recommendation to themselves then 😆

      2 replies 0 retweets 0 likes
    3. Yehuda Katz  🥨‏Verified account @wycats Jan 13
      Replying to @spion @lucasazzola and

      As a supporter of no-semi style, would you be in favor of mandatory semicolons for class fields?

      1 reply 0 retweets 0 likes
    4. Gorgi Kosev‏ @spion Jan 13
      Replying to @wycats @lucasazzola and

      As a supporter I don't personally mind the new ASI hazards. The bad ones. The worst one is `async`, so if I could get one wish, it would be to get rid of that.

      2 replies 0 retweets 0 likes
    5. Yehuda Katz  🥨‏Verified account @wycats Jan 13
      Replying to @spion @lucasazzola and

      Get rid of it how?

      1 reply 0 retweets 0 likes
    6. Gorgi Kosev‏ @spion Jan 13
      Replying to @wycats @lucasazzola and

      If possible, I would special-case the async "field name" in class bodies, make it not trigger ASI. (make it behave just like `get`)

      1 reply 0 retweets 0 likes
    7. Yehuda Katz  🥨‏Verified account @wycats Jan 13
      Replying to @spion @lucasazzola and

      Outside of classes, async is already a variable, so it requires a NoLineTerminatorHere. You're saying in classes relax that restriction so that you would *require* a semi for a field named get, set or async?

      1 reply 0 retweets 0 likes
    8. Gorgi Kosev‏ @spion Jan 13
      Replying to @wycats @lucasazzola and

      I thought fields named `get` and `set` already require a semicolon? I thought `async` should be included too. https://tc39.github.io/proposal-class-fields/#sec-asi-hazards-in-class-bodies …

      1 reply 0 retweets 0 likes
    9. Yehuda Katz  🥨‏Verified account @wycats Jan 13
      Replying to @spion @lucasazzola and

      Sorry. (this space is confusing with all the double negatives inside of double negatives). We could relax NoLineTerminatorHere for async methods in classes, but we won't be able to do that again for new contextual keywords later. Also inconsistency with async functions.

      2 replies 0 retweets 0 likes
    10. Gorgi Kosev‏ @spion Jan 13
      Replying to @wycats @lucasazzola and

      Consistency is impossible, but I see your other point. What if additionally semicolons are required for fields without an initializer?

      1 reply 0 retweets 0 likes
      Yehuda Katz  🥨‏Verified account @wycats Jan 13
      Replying to @spion @lucasazzola and

      Would that be acceptable to people who want a no-semi style?

      12:56 PM - 13 Jan 2018
      2 replies 0 retweets 0 likes
        1. New conversation
        2. Yehuda Katz  🥨‏Verified account @wycats Jan 13
          Replying to @wycats @spion and

          (I would expect fields without initializers to be used along with documentation, which would also increase the risk of no-semis, since the offending "next line" could be way later)

          1 reply 0 retweets 0 likes
        3. Gorgi Kosev‏ @spion Jan 13
          Replying to @wycats @lucasazzola and

          I would probably initialise those to `undefined` explicitly and use a noUninitializedClassFields linter rule. Hope that typed dialects could take advantage of the type declaration to do better ASI without requiring initialisation.

          2 replies 0 retweets 0 likes
        4. Yehuda Katz  🥨‏Verified account @wycats Jan 13
          Replying to @spion @lucasazzola and

          Would users of standard accept this compromise? /cc @feross It's not ridiculous and I'd be willing to give it a try at TC39. Aside: we need more representation from users of this style on TC39.

          3 replies 0 retweets 0 likes
        5. Daniel Ehrenberg‏ @littledan Jan 13
          Replying to @wycats @spion and

          I don't really understand. We decided to support ASI in field initializers fully specifically to support demands for this behavior from people who use the no semicolon style. Would that group prefer to be forced to use semicolons to avoid creating new ASI hazards?

          2 replies 0 retweets 2 likes
        6. Daniel Ehrenberg‏ @littledan Jan 13
          Replying to @littledan @wycats and

          We came to this decision partly because we do have some representation on the committee from no semicolon programmers, e.g. @Keithamus

          1 reply 0 retweets 0 likes
        7. Keith Cirkel‏ @Keithamus Jan 13
          Replying to @littledan @wycats and

          This is correct, and my objection was on the grounds that (barring straight for loops) semis are not a _required_ part of syntax. Saying semis should be required without initialisers, but not required with them seems like a worse decision though

          2 replies 0 retweets 1 like
        8. BrendanEich‏Verified account @BrendanEich Jan 13
          Replying to @Keithamus @littledan and

          Is the without-init/not-with-init requirement a serious proposal or a strawman? That is not a proposal of the "ASI applies in class bodies" or "ASI does not apply in class bodies" form.

          1 reply 0 retweets 0 likes
        9. Yehuda Katz  🥨‏Verified account @wycats Jan 13
          Replying to @BrendanEich @Keithamus and

          It's a serious proposal, but unsure if it has legs. It allows broad use of no-semis with a small additional restriction for unusual cases. Not so different from other standardjs mitigations like requiring {} for if() etc.

          1 reply 0 retweets 0 likes
        10. 13 more replies
        1. New conversation
        2. Gorgi Kosev‏ @spion Jan 13
          Replying to @wycats @lucasazzola and

          Can't speak for everyone, but it would be to me. (But to be honest, without decorators I don't see why I would define uninitialised fields anyway)

          1 reply 0 retweets 0 likes
        3. Yehuda Katz  🥨‏Verified account @wycats Jan 13
          Replying to @spion @lucasazzola and

          Yehuda Katz  🥨 Retweeted Yehuda Katz  🥨

          I followed uphttps://twitter.com/wycats/status/952283699592052736 …

          Yehuda Katz  🥨 added,

          Yehuda Katz  🥨Verified account @wycats
          Replying to @wycats @spion and 8 others
          (I would expect fields without initializers to be used along with documentation, which would also increase the risk of no-semis, since the offending "next line" could be way later)
          0 replies 0 retweets 0 likes
        4. End of conversation

      Loading seems to be taking a while.

      Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

        Promoted Tweet

        false

        • © 2018 Twitter
        • About
        • Help Center
        • Terms
        • Privacy policy
        • Cookies
        • Ads info