@cmuratori @rygorous @Jonathan_Blow Why settle for that constraint?
@cmuratori @rygorous @Jonathan_Blow Not the best example, but it should be trivial to parse that. It's very obvious when you look at it.
-
-
@cmuratori@rygorous@Jonathan_Blow But like, you can easily construct things with that where the LL(1) parser has no idea what's going on. -
@cmuratori@rygorous@Jonathan_Blow A very simple backtracking parser, on the otherhand, has no problem with that, right. - Show replies
New conversation -
-
-
@cmuratori@Jonathan_Blow Your backtracking parser is going to, arbitrarily (and possibly inconsistently), pick one of those. -
@rygorous@Jonathan_Blow You said you were out! You cannot come back in!
End of conversation
New conversation -
-
-
@cmuratori@rygorous@jonathan_blow That sounds dangerously close to "do what I mean!". -
@TangentVector Yes indeed, and once you go to my example of "<<<<x>>" you start to see the problem. :) (3 possible parses w/ backtracking)
End of conversation
New 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.