-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
more specific location for syntax errors #6179
Comments
Unless this is accompanied by a pull request to improve the parser, I'm going to close this as busywork that will most likely fall on @JeffBezanson. An unbounded amount of time and effort can be put into making the parser handle syntax errors better, but it's a matter of diminishing returns. That's not to say that improvements aren't welcomed – we will happily merge pull requests that improve error messages! |
I'm re-opening this. Duplicates of this issue keep appearing because Julia's syntax errors are often inordinately vague at the moment; we aren't anywhere close to the point of diminishing returns yet. We need an issue as a place to both centralize complaints and to track work that is being done to improve matters. |
#4744 ? |
@tkelman, that issue is for generic improvements to error messages; this one is specific to line numbers. |
Ooh! This is going to be really nice! I added a |
I just ran into this. I'm definitely not the most experienced Julian, but we have to be able to do better than
for
If you're typing it in line by line, the experience is fine since the error comes right after you hit the offending line, but if you're copy-pasting code in, not having any indication what line was the problem is really annoying. |
|
test.jl:
julia test.jl
:ERROR: syntax: unexpected "]" in argument list in include_from_node1 at loading.jl:120 while loading test.jl, in expression starting on line 1
It would be better if the error will be point out more precisely (instead of just pointing at the beginning of the function).
The text was updated successfully, but these errors were encountered: