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.

This is the legacy version of twitter.com. We will be shutting it down on June 1, 2020. Please switch to a supported browser, or disable the extension which masks your browser. You can see a list of supported browsers in our Help Center.

  • 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
pcwalton's profile
Patrick Walton
Patrick Walton
Patrick Walton
@pcwalton

Tweets

Patrick Walton

@pcwalton

Research engineer at Mozilla

San Francisco, CA
pcwalton.github.io
Joined November 2009

Tweets

  • © 2020 Twitter
  • About
  • Help Center
  • Terms
  • Privacy policy
  • Imprint
  • 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. Patrick Walton‏ @pcwalton 19 Aug 2019
      • Report Tweet
      • Report NetzDG Violation

      I rag on “if err != nil { return err }”, but I can sort of understand where people who prefer it to try/exceptions are coming from, even though I completely disagree. But I can’t even begin to understand people who prefer hand-written state machines to async/await.

      11 replies 6 retweets 94 likes
    2. Tony “Abolish ICE” Arcieri  🦀‏ @bascule 19 Aug 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @pcwalton

      Whenever people talk Go's "readability", I can't get over how every line of actual code is buried in an additional 3+ lines of redundant error handling boilerplate. "...but you get used to it!" is the counterargument, and one I think can be used to justify anything as "readable"

      4 replies 4 retweets 33 likes
    3. Daniel‏ @dehaavi 19 Aug 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @bascule @pcwalton

      If you actually add some valuable context and not just "return err", it makes a lot of sense. I like it, because the control flow is so explicit.

      1 reply 0 retweets 1 like
    4. Tony “Abolish ICE” Arcieri  🦀‏ @bascule 19 Aug 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @dehaavi @pcwalton

      Like this? 😜 https://github.com/golang/go/issues/19991 …pic.twitter.com/0CmFlG1TUQ

      1 reply 1 retweet 3 likes
    5. Daniel‏ @dehaavi 19 Aug 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @bascule @pcwalton

      Wow, that is just ugly. That is not the price I'm going to pay for saving one line of code. I mostly use fmt.Errorf("failed to foo with bar: %s", err), which not only adds context, but at the same time, tells the reader what I was actually trying to do, thus documenting the code

      1 reply 0 retweets 0 likes
      Patrick Walton‏ @pcwalton 19 Aug 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @dehaavi @bascule

      In Rust I can write try!(f(…).map_err(MyErr::FooFailed)); which is just as clear and shorter.

      2:09 PM - 19 Aug 2019
      • 2 Likes
      • Karoofish 👻🎃 Status Quo 🎃👻
      2 replies 0 retweets 2 likes
        1. New conversation
        2. Patrick Walton‏ @pcwalton 19 Aug 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @pcwalton @dehaavi @bascule

          I think the “explicit control flow” buys nothing at all when panics can cause invisible stack unwinding almost everywhere.

          3 replies 0 retweets 8 likes
        3.  👻 🎃 Status Quo  🎃 👻‏ @KardOnIce 19 Aug 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @pcwalton @dehaavi @bascule

          Invisible code paths are such a dangerous concept, IMO. In C++, there's a reason you have to manage resources with a designated class, and that's because an invisible error might be thrown, at best causing resource leaks.

          1 reply 0 retweets 0 likes
        4. 2 more replies
        1. New conversation
        2. Tony “Abolish ICE” Arcieri  🦀‏ @bascule 19 Aug 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @pcwalton @dehaavi

          In my experience over half the time errors can be propagated without additional context. So map_err is still more succinct for the cases where you want to add it, and then it's an even bigger win when you don't.

          1 reply 0 retweets 2 likes
        3. Patrick Walton‏ @pcwalton 19 Aug 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @bascule @dehaavi

          Yeah, I rarely ever bother. (Though GPU programming is a little weird because you can’t afford to synchronously check errors for performance reasons—error checking is an async operation. So I don’t actually deal with errors in Rust as much as others do nowadays.)

          0 replies 0 retweets 2 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

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