Ilya Salauyeu

@mpkorstanje > update the specification to match your implementation No, I'm trying to **introduce formal specification** as there is none yet. > does not accept the superset of all Cucumber...

@mattwynne thanks for the invitation! But I'd like to have discussion here manly for 2 reasons: 1. In my experience Slack conversations have tendency to branch off into some other...

@mpkorstanje > To fix the context sensitive grammar in such a way that a the EBNF can be logically derived from it. I don't understand what `EBNF can be logically...

@mpkorstanje 1. I want to guarantee that Rust implementation is correct. For that I need to formalize Cucumber Expressions language. While you are asking me to fix language which is...

@tyranron > programmable way for mapping "formal spec" AST into the current one, or vice versa Simply mapping from formal spec into superset grammar won't give us much info. It's...

@mattwynne I also noticed one interesting implementation detail. Whitespaces are treated as a some sort of special case ```yml --- expression: three hungry/blind mice expected_ast: type: EXPRESSION_NODE start: 0 end:...

@mpkorstanje > I'm not sure about the point you are making. Your previous argument was about not being able to change the grammar into being context-free, as current implementations are...

@mpkorstanje this is significant, because real lookahead requires context-sensitive grammar, while implemented one doesn't. I believe that it's possible to formalise pretty easy-to-understand context-free grammar which fully compliant with implementation.

@mpkorstanje > That change should be reflected in the implementation of the alternationParser. I didn't mean old proposal when said `I believe that it's possible to formalise pretty easy-to-understand context-free...

@tgsmith61591 can you share a little bit more about the characteristics of the testing suite? Is it async or sync heavy, or maybe appropriately both? Can you share the `World`...