Parse errors are hard to understand. These errors come directly from the PEST grammar, which no Simfony developer will have read. It would be better to accept incomplete program components during parsing and to produce an expressive user-facing error when the AST is generated.
#56 (comment)
Like, right now if you remove type annotations from your example programs you get something like expected match_pattern but it'd be nicer if we'd parse these things, mark them as "unknown type" and then during AST conversion we'd give the user an error like "No type was specified for x. You need to provide a type annotation, like x: bool."
The scope of this change is unclear, but grammar errors are hard to understand so we never want to show them to users.
Parse errors are hard to understand. These errors come directly from the PEST grammar, which no Simfony developer will have read. It would be better to accept incomplete program components during parsing and to produce an expressive user-facing error when the AST is generated.
#56 (comment)
The scope of this change is unclear, but grammar errors are hard to understand so we never want to show them to users.