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. qualia are a fuck‏ @__anp__ 11 Jan 2019
      • Report Tweet
      • Report NetzDG Violation

      reading an EPIC summary of some @rustlang syntax discussion about my favorite--the turbofish! as much as i love me some ergonomics, allowing unbounded syntax lookahead to parse rust makes me realllllllly sadhttps://github.com/rust-lang/rfcs/pull/2544#issuecomment-453653184 …

      1 reply 0 retweets 17 likes
      Show this thread
    2. qualia are a fuck‏ @__anp__ 11 Jan 2019
      • Report Tweet
      • Report NetzDG Violation

      to be clear, this case is obviously so rare, who cares? but as is clear from centril's post, *precedent matters* in social organizations. seems like a super unfun precedent to set to me

      1 reply 1 retweet 4 likes
      Show this thread
    3. qualia are a fuck‏ @__anp__ 11 Jan 2019
      • Report Tweet
      • Report NetzDG Violation

      i believe at some point @graydon_pub has had some interesting things to say about token lookahead too

      1 reply 0 retweets 1 like
      Show this thread
    4. Graydon Hoare‏ @graydon_pub 11 Jan 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @__anp__

      I wanted rust to stay LL(k) ideally for k=1. I also wanted its lexical grammar to stay regular. I was sad when it lost the latter, am sad if it's currently losing the former, and strongly reject the "it's not so bad" narrative in the grammatical complexity section of that RFC.

      1 reply 1 retweet 19 likes
    5. Graydon Hoare‏ @graydon_pub 11 Jan 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @graydon_pub

      Frankly I am a bit despairing at the degree to which this "it's not so bad, let's just keep adding costs" thinking pervades the ongoing trajectory of the thing. I said so recently and publicly and it got a rebuke from the language team that IMO missed the point entirely. So: sad.

      3 replies 5 retweets 37 likes
    6. Manish‏ @ManishEarth 11 Jan 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @graydon_pub

      i kinda agree, there have been multiple times where i've brought up hidden costs and kinda been sidestepped :/ (the breaking change bit also bothers me, rust *already* has issues being stable with larger codebases. firefox has hit this a bunch of times)

      3 replies 0 retweets 7 likes
    7. Patrick Walton‏ @pcwalton 11 Jan 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @ManishEarth @graydon_pub

      I’m normally conservative with language changes these days, but this is one area in which I don’t actually care. I think LL(k) is a property that doesn’t matter at all.

      3 replies 0 retweets 4 likes
    8. Patrick Walton‏ @pcwalton 11 Jan 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @pcwalton @ManishEarth @graydon_pub

      If you’re parsing Rust for any practical purpose, the complexity class of the grammar isn’t in the top 10 things that are difficult. It isn’t even in the top 100.

      1 reply 0 retweets 7 likes
    9. Patrick Walton‏ @pcwalton 11 Jan 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @pcwalton @ManishEarth @graydon_pub

      The things that make parsing languages difficult are things like C’s lexer hack, or the way C++’s template expansion affects parsing. Not theoretical complexity class of the grammar.

      3 replies 0 retweets 2 likes
    10. qualia are a fuck‏ @__anp__ 11 Jan 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @pcwalton @ManishEarth @graydon_pub

      something something vim plug-ins?

      1 reply 0 retweets 2 likes
      Patrick Walton‏ @pcwalton 11 Jan 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @__anp__ @ManishEarth @graydon_pub

      Vim plugins for syntax coloring can’t and don’t parse the grammar. More complex IDE support will just use libsyntax and be done with it.

      4:59 PM - 11 Jan 2019
      • 1 Like
      • qualia are a fuck
      2 replies 0 retweets 1 like
        1. New conversation
        2. russell‏ @rpjohnst 11 Jan 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @pcwalton @ManishEarth @graydon_pub

          I'd rather we not conflate all rust parsers into libsyntax- independent implementations are good for keeping the spec unambiguous and understandable

          1 reply 0 retweets 1 like
        3. Patrick Walton‏ @pcwalton 11 Jan 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @rpjohnst @ManishEarth @graydon_pub

          It won’t prevent independent implementations. It’s not like unbounded lookahead is that much of a burden in practice!

          1 reply 0 retweets 0 likes
        4. 6 more replies
        1. New conversation
        2. Manish‏ @ManishEarth 11 Jan 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @pcwalton @graydon_pub

          well, libsyntax2, IDEs have different design requirements for parsers, chiefly they need to have *really* good recovery and be totally okay with partial nodes. That's kinda what the plan is with libsyntax2, which rustc probably won't use

          1 reply 0 retweets 1 like
        3. Patrick Walton‏ @pcwalton 11 Jan 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @ManishEarth @graydon_pub

          What does unbounded lookahead have to do with recovery?

          1 reply 0 retweets 0 likes
        4. 1 more reply

      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