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
yoshuawuyts's profile
yosh
yosh
yosh
@yoshuawuyts

Tweets

yosh

@yoshuawuyts

Software researcher. he/they

Berlin, UTC+2
blog.yoshuawuyts.com
Joined May 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. yosh‏ @yoshuawuyts 22 Mar 2019
      • Report Tweet
      • Report NetzDG Violation

      Stack traces, human panic, and failure::Context are essentially runtime docs. They provide contextual information when something goes wrong. Output depends on what went wrong. Also you'll never want them ahead of time, but only when inspecting the program.

      1 reply 0 retweets 11 likes
      Show this thread
    2. yosh‏ @yoshuawuyts 22 Mar 2019
      • Report Tweet
      • Report NetzDG Violation

      I guess the compiler error messages are quite similar. Super contextual, and completely dependent on the input state you gave it. Imagine if we could make a similar leap the compiler has for compilation errors, but for in-program runtime error reporting. We should experiment :D

      1 reply 2 retweets 13 likes
      Show this thread
    3. yosh‏ @yoshuawuyts 22 Mar 2019
      • Report Tweet
      • Report NetzDG Violation

      (oh oh oh, just like, imagine if debug Rust could point to the line in source that the program broke, and explain how it broke, and why. Would be so much better than staring at a 50 line stack trace)

      3 replies 0 retweets 9 likes
      Show this thread
    4. Manish‏ @ManishEarth 22 Mar 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @yoshuawuyts

      The problem is code ownership and responsibilities, what invariant went wrong is not something the compiler can figure out because it's a higher level concept not encoded in the type system. (If it could be, it wouldn't be a panic)

      1 reply 0 retweets 1 like
    5. Manish‏ @ManishEarth 22 Mar 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @ManishEarth @yoshuawuyts

      It's often the first frame (or in the case of unwrap, the second frame), but not always. (There's an rfc for implicit caller location that makes this somewhat nicer for the semi-common case)

      1 reply 0 retweets 0 likes
      yosh‏ @yoshuawuyts 22 Mar 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @ManishEarth

      Oh haha, yeah I don't disagree. Guess I should've been more specific. Currently we have a known TLS bug in a program. On invalid access instead of just panicking it'd be wild if we could track which thread failed, and show the line of code where the thread was spawned.

      10:28 AM - 22 Mar 2019 from Berlin, Germany
      • 1 Like
      • Manish
      1 reply 0 retweets 1 like
        1. New conversation
        2. yosh‏ @yoshuawuyts 22 Mar 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @yoshuawuyts @ManishEarth

          I'm suspecting there might be more cases like these around stdlib. For example locks is another I'm curious about. But just in general if we could log the source lines corresponding to the failure I think we could really make some leaps.

          1 reply 0 retweets 1 like
        3. Manish‏ @ManishEarth 22 Mar 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @yoshuawuyts

          Ah tracking threads is possible. When you spawn threads you can name them, fwiw, and that shows up in the backtrace.

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