-
Notifications
You must be signed in to change notification settings - Fork 187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
malformed raw string literal not captured #892
Comments
Could you elaborate on what's the error here? Here's what I get at HEAD:
Just that the |
Yes. Should be titled that the line number is not captured. |
3 tasks
AshesITR
added a commit
that referenced
this issue
Feb 15, 2022
* Improve line location information for R parse errors I chose to use a script in `data-raw` to auto-generate the required parse error regexes and store them in .parse_error_regexes in `R/sysdata.rda`. `get_source_expressions()` then uses a for-loop after the initial (manual) message checks to see if a parse error with line information was matched. Fixes #892 Fixes #894 * [x] implement * [x] add tests * [x] add NEWS bullet * fix auto-wrap * fix double-escape for \ in regexes add tests for one-past EOF line number and for \ in error message * improve message extraction * change approach to generic regex without sysdata * incorporate review suggestions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The syntax error of the raw string in the following code is not captured:
where error has the number of line:
The text was updated successfully, but these errors were encountered: