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 Feb 2
      • Report Tweet
      • Report NetzDG Violation

      Rust compiler performance is hard to have meaningful discussions about because: (1) There’s no single part of the compiler which is slow. In fact the compiler is pretty well optimized.

      8 replies 11 retweets 152 likes
      Show this thread
      Patrick Walton‏ @pcwalton Feb 2
      • Report Tweet
      • Report NetzDG Violation

      (2) There’s no high-profile language design decision you can point to and say “aha, that was a mistake!” No header files, for example. The slowness comes from a lot of smaller things that have real benefits, such as the borrow check.

      11:18 AM - 2 Feb 2020
      • 4 Retweets
      • 97 Likes
      • Jashank Jeremy Manish Kyle J Strand Benjamin Fry🦀👾⚙️ Mohamed Elqdusy YT. Hsieh Antariksh Chavan Daniel Dettlaff plutoo
      10 replies 4 retweets 97 likes
        1. New conversation
        2. Zorro Notorious MEB he / him‏ @znmeb Feb 2
          • Report Tweet
          • Report NetzDG Violation
          Replying to @pcwalton

          I don't know about whether this is meaningful to a language like Rust, but back in the 1960s / 70s when there was massive investment in Fortran compiler technology, there were two types of compilers:

          1 reply 0 retweets 0 likes
        3. Zorro Notorious MEB he / him‏ @znmeb Feb 2
          • Report Tweet
          • Report NetzDG Violation
          Replying to @znmeb @pcwalton

          1. Highly optimizing compilers - they spent a lot of compile time grinding out the best code they could. All the tricks in the book were fair game. 2. "Student" compilers, like WATFOR - they were optimized for compile speed. They were glorified macro assemblers.

          1 reply 0 retweets 1 like
        4. 4 more replies
        1. Rik Arends‏ @rikarends Feb 2
          • Report Tweet
          • Report NetzDG Violation
          Replying to @pcwalton

          Seems like there may be only one path then: be more incremental. First time compile is alright since you can sortof manage that yourself by not snowballing deps. But i'd love the ability to change small bits of code and hotload them rapidly. Doing that now for shaders but yea.

          0 replies 0 retweets 6 likes
          Thanks. Twitter will use this to make your timeline better. Undo
          Undo
        1. New conversation
        2. Darius Jahandarie‏ @djahandarie Feb 2
          • Report Tweet
          • Report NetzDG Violation
          Replying to @pcwalton

          I think the basic architectural decision to make the compiler offline (instead of an online differential/incremental dataflow) is one thing that makes it “slow” (where “slow” is to be understood as something which lengthens the development feedback cycle).

          2 replies 0 retweets 5 likes
        3. Paolo G. Giarrusso‏ @Blaisorblade Feb 2
          • Report Tweet
          • Report NetzDG Violation
          Replying to @djahandarie @pcwalton

          Honest question: is there any evidence that *fine-grained* incrementalization would help *in a compiler for such a complex language*? Embarrassingly parallel tasks parallelize well, but compilation ain't it, even if you ignore monomorphization.

          1 reply 0 retweets 1 like
        4. 4 more replies
        1. Saoirse Shipwreckt‏ @withoutboats Feb 2
          • Report Tweet
          • Report NetzDG Violation
          Replying to @pcwalton

          I think there are some clear unforced errors like name resolution (though these matter more for IDE responsiveness than batch throughput)

          0 replies 0 retweets 4 likes
          Thanks. Twitter will use this to make your timeline better. Undo
          Undo
        1. C�cile Tonglet  🦀‏ @CecileTonglet Feb 4
          • Report Tweet
          • Report NetzDG Violation
          Replying to @pcwalton

          I guess what you mean is that compiler safety comes at the price of compilation time... this sounds logical

          0 replies 0 retweets 3 likes
          Thanks. Twitter will use this to make your timeline better. Undo
          Undo
        1. New conversation
        2. Connie Hilarides‏ @Connicpu Feb 2
          • Report Tweet
          • Report NetzDG Violation
          Replying to @pcwalton

          Is the borrow checker even what's slow? I always thought llvm was the big bottle neck even in debug builds

          1 reply 0 retweets 1 like
        3. Anthony Ramine‏ @nokusu Feb 4
          • Report Tweet
          • Report NetzDG Violation
          Replying to @Connicpu @pcwalton

          LLVM is the bottleneck for Servo at the very least.

          0 replies 0 retweets 1 like
        4. End of conversation
        1. New conversation
        2. PM_ME_CURSED_HACKS‏ @theFerdi265 Feb 3
          • Report Tweet
          • Report NetzDG Violation
          Replying to @pcwalton

          could borrow-check be cached between compilations? e.g., if borrow check passes for a debug build, then don't do it when release building if the code didn't change. Or is borrow-check dependant on which compiler options are set, so caching between debug/release won't work?

          1 reply 0 retweets 0 likes
        3. Anthony Ramine‏ @nokusu Feb 4
          • Report Tweet
          • Report NetzDG Violation
          Replying to @theFerdi265 @pcwalton

          The code itself is dependent on whether you want debug or release, with debug_assert, cfg, etc. And the borrow checker is not a bottleneck anyway.

          0 replies 0 retweets 1 like
        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