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. whitequark‏ @whitequark 7 Sep 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @RichFelker

      most languages don't just ignore nonzero syscall return codes by default, they turn them into exceptions or panics or something like that

      2 replies 0 retweets 0 likes
    2. Rich Felker‏ @RichFelker 7 Sep 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @whitequark

      Write error is a very normal condition you have to expect, however it's reported, though. And if you're implementing std utilities you need to translate it into the specified effect on exit status to match expectations of invoking programs/scripts...

      1 reply 0 retweets 2 likes
    3. Rich Felker‏ @RichFelker 7 Sep 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @RichFelker @whitequark

      So it sounds like these tool replacements written in Rust are just sloppily written.

      1 reply 0 retweets 2 likes
    4. whitequark‏ @whitequark 7 Sep 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @RichFelker

      sort of, but the issue goes deeper: the standard library makes it extra hard to actually react to the write error because of the way println!() is designed, arguably a design mistake

      1 reply 0 retweets 2 likes
    5. Ada Worcester  🏳️‍⚧️‏ @pikhq 7 Sep 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @whitequark @RichFelker

      I really don't get why basic stuff in the stdlib panics on failures. You have an error handling facility, people. Use it.

      1 reply 0 retweets 1 like
    6. Rich Felker‏ @RichFelker 7 Sep 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @pikhq @whitequark

      It actually panics rather than throwing or returning an error?!

      2 replies 0 retweets 0 likes
    7. Ada Worcester  🏳️‍⚧️‏ @pikhq 7 Sep 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @RichFelker @whitequark

      Yep. You have to use different functions instead to actually catch errors on writes to stdout.

      2 replies 0 retweets 1 like
    8. Ada Worcester  🏳️‍⚧️‏ @pikhq 7 Sep 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @pikhq @RichFelker @whitequark

      Essentially, in Rust you should mistrust any function that does some syscall and doesn't return Result IMO

      1 reply 2 retweets 5 likes
    9. Rich Felker‏ @RichFelker 7 Sep 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @pikhq @whitequark

      BTW I don't mean to dunk on Rust here. Rather I want to draw out and understand pitfalls in case I end up using it in future, and to encourage others to be aware of them.

      1 reply 0 retweets 2 likes
    10. Laurent Bercot‏ @laurentbercot 7 Sep 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @RichFelker @pikhq @whitequark

      Sounds like a good opportunity to dunk on the Rust stdlib though. Making a language that's supposed to be safe, and not handling write errors in very standard functions in the stdlib sounds like a major misdesign, a newbie mistake that shows terrible lack of experience with Unix.

      2 replies 0 retweets 0 likes
      Patrick Walton‏ @pcwalton 7 Sep 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @laurentbercot @RichFelker and

      It checks errors and panics. This was a design decision to minimize the amount of noise for common cases. println! is a convenience macro. println!(“foo”) is shorthand for: writeln!(std::io::stdout(), “foo”).unwrap()

      8:33 PM - 7 Sep 2019
      1 reply 0 retweets 0 likes
        1. New conversation
        2. Patrick Walton‏ @pcwalton 7 Sep 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @pcwalton @laurentbercot and

          It was *always* intended that print/println is a convenience macro, and write/writeln is the one you use for proper error handling. Maybe that was not made clear enough, but that was the design.

          1 reply 0 retweets 1 like
        3. Rich Felker‏ @RichFelker 7 Sep 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @pcwalton @laurentbercot and

          In that case the tutorials/hello worlds should be teaching write/writeln and pretending println doesn't exist...

          1 reply 0 retweets 0 likes
        4. 2 more replies

      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