strager
> you really should read up a bit about _recursive descent parsers_ and why they do not use regular expressions most of the time. @KeremArdicli is talking about using regex...
Are you getting an error message?
Errors should appear in your file with the `.py` suffix. It's a text file.
Proposed logic: After parsing the `{` `}` body of an `if`, check if the next token is `Token_Type::kw_if` and if `has_leading_newline` is false. If yes, then warn.
@qnguyen1013 Sure thing! Here are our contribution guides: https://quick-lint-js.com/contribute/ If you need any help, let me know.
This is a great idea! I'll put 12$ on it.
`() => await;` is legal in script mode. https://astexplorer.net/#/gist/ce7f1c8465166e5dd8923f21a71e6c5a/ca4992a4e78c2dfe0dbda6ade70d4700e7ce7efc quick-lint-js currently permits code which is legal in either script or module mode. It would be nice to have a better...
I think this should be simple. In `parse_and_visit_statement`, when we parse an expression, and the expression is an arrow function, report a warning.
> @strager which of these should report `error_unused_arrow_function`: 1, 2, and 3. 4 should report a different diagnostic (E0105).
@jr-boney I don't see any unused arrow expressions in your code. Are you seeing a bug in quick-lint-js related to your code?