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 …
-
Show this thread
-
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 likesShow this thread -
i believe at some point
@graydon_pub has had some interesting things to say about token lookahead too1 reply 0 retweets 1 likeShow this thread -
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 -
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 -
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 -
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 -
Replying to @pcwalton @ManishEarth
It doesn't matter practically for something doing a complete parse of the language; it does matter for partial parses and sub-parse algorithms like error recovery and structural chunking in editors; and it matters more in the sense that a limit helps you control costs.
1 reply 0 retweets 1 like
I don’t see how this affects error recovery at all. You just backtrack.
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.