@nothings @won3d @JasperBekkers @hamishtodd1 It also (practically) broadens the language set and improves error tolerance/reporting.
-
-
Replying to @cmuratori
@cmuratori@won3d@JasperBekkers@hamishtodd1 Need a proof of concept for the latter claim, since yacc demonstrably ruins error reporting.4 replies 0 retweets 0 likes -
Replying to @nothings
@nothings@cmuratori@won3d@JasperBekkers@hamishtodd1 The real problem is that nobody ever bothers with replacing default yacc error msgs.3 replies 0 retweets 0 likes -
Replying to @rygorous
@rygorous@cmuratori@won3d@JasperBekkers@hamishtodd1 Hundreds, because you need to make the whole thing LALR & disambiguated etc.1 reply 0 retweets 0 likes -
Replying to @nothings
@nothings@rygorous@won3d@JasperBekkers@hamishtodd1 LALR disambiguation isn't relevant anymore. Backtracking is where it's at, IMO.4 replies 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@nothings@won3d@JasperBekkers@hamishtodd1 Anything that ever sees large projects (or hostile input) better be guaranteed O(n).1 reply 0 retweets 0 likes -
Replying to @rygorous
@rygorous@nothings@won3d@JasperBekkers@hamishtodd1 That's performance, not convenience. Though I'm not sure I agree even then.2 replies 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori Again, I don't care for your convenience. This is a correctness + sanity issue.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori I want nothing to do with any language (or impl) that needs backtracking. Limited lookahead should be enough for anyone!1 reply 0 retweets 0 likes
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.