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
davidtolnay's profile
David Tolnay
David Tolnay
David Tolnay
@davidtolnay

Tweets

David Tolnay

@davidtolnay

Menlo Park, CA
Joined October 2018

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. Yaah  🍑 🦀 ☕‏ @yaahc_ 17 Dec 2019
      • Report Tweet
      • Report NetzDG Violation

      So here's an Idea. Pluggable formatters for your error messages. imagine doing `type Error = anyhow::Error<Formatter = RootCauseLast>` Where you can define your own formatters and plug them in or use some predefined ones and the formatter is set to a specific one by default.pic.twitter.com/W1gmaGFku5

      5 replies 0 retweets 24 likes
    2. Katharina  🦋 Fey‏ @spacekookie 17 Dec 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @yaahc_

      I really like this idea! I've been thinking about some stuff along these lines in regards to the return result from main issue that doesn't really make it any nicer for users because those errors use debug, not display...

      1 reply 0 retweets 3 likes
    3. Yaah  🍑 🦀 ☕‏ @yaahc_ 17 Dec 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @spacekookie

      Yea, it using Debug isn't really ideal. @davidtolnay wants to add an `is_termination()` method to Formatter that would let you write debug impls that behave differently when being rendered by main, and I've told him I'm down to help write the RFC for it, but thats a long way off.

      1 reply 0 retweets 1 like
    4. Yaah  🍑 🦀 ☕‏ @yaahc_ 17 Dec 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @yaahc_ @spacekookie @davidtolnay

      For now I think the correct pattern is to have an Error Reporting type that is what you return from main, rather than errors themselves, and it has a debug impl that is really a display impl for main.

      1 reply 0 retweets 1 like
    5. Katharina  🦋 Fey‏ @spacekookie 17 Dec 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @yaahc_ @davidtolnay

      Agreed, that would be much better. Tbh having a debug formatter that behaves differently feels a bit yikes and like we're gonna regret that even more than the correct errors using debug issue lol.

      1 reply 0 retweets 2 likes
    6. Katharina  🦋 Fey‏ @spacekookie 17 Dec 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @spacekookie @yaahc_ @davidtolnay

      Alternatively, to what extent can these "error return formatter" be auto derived? Might be worth looking into what kind of ergonomics we can have there

      1 reply 0 retweets 1 like
    7. MⒶrtin HⒶboⓋštiak [BEFORE! Jan/3➞₿ 🔑∎, LNP/BP]‏ @kixunil 17 Dec 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @spacekookie @yaahc_ @davidtolnay

      It's possible to write a wrapper that redirects Debug to Display. Overall, I agree that rushing stabilization to use Debug was a great mistake. That formatter method sounds like hack. (But thanks God at least that is possible.)

      2 replies 0 retweets 1 like
    8. David Tolnay‏ @davidtolnay 17 Dec 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @kixunil @spacekookie @yaahc_

      I strongly disagree that it was a mistake, Display would be worse. In order for applications to have control over rendering cause chains, error types are required to *not* print their causes from the Display impl. The right approach is exposing is_termination on Formatter.

      1 reply 0 retweets 1 like
    9. MⒶrtin HⒶboⓋštiak [BEFORE! Jan/3➞₿ 🔑∎, LNP/BP]‏ @kixunil 17 Dec 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @davidtolnay @spacekookie @yaahc_

      Huh? I haven't heard this rule yet. Where is it documented? Looks like I have every single library wrong. Anyway, unless there's some kind of new attribute for derive(Debug), it looks like implementing errors will be a huge pain.

      1 reply 0 retweets 0 likes
      David Tolnay‏ @davidtolnay 17 Dec 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @kixunil @spacekookie @yaahc_

      Well think about how @yaahc_'s proposal at the top of thread would be impossible if every layer of your error were incorrectly always printing every lower layer of the error too. There would be no way for a library to iterate the chain and print in the intended order and layout.

      9:06 AM - 17 Dec 2019
      • 1 Like
      • Yaah 🍑🦀☕
      1 reply 0 retweets 1 like
        1. New conversation
        2. MⒶrtin HⒶboⓋštiak [BEFORE! Jan/3➞₿ 🔑∎, LNP/BP]‏ @kixunil 17 Dec 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @davidtolnay @spacekookie @yaahc_

          That's true, this should be documented better I think. I will need to fix all my stuff now. :) Regarding is_termination() - makes sense now, but unless I'm missing something, people will have to implement Debug manually, or there needs to be a new derive or attribute, right?

          2 replies 0 retweets 1 like
        3. David Tolnay‏ @davidtolnay 17 Dec 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @kixunil @spacekookie @yaahc_

          anyhow::Error prints using the Display impls of the cause chain so there isn't a need for a new derive at each level other than Display, which already exists in the thiserror or displaydoc crates.

          1 reply 0 retweets 1 like
        4. 5 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