-
-
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
LineNumber nodes in :toplevel expressions are ignored #28990
Labels
Comments
At the same time I notice |
JeffBezanson
added a commit
that referenced
this issue
Jan 7, 2019
This gives better location info inside `:toplevel` expressions and for REPL inputs that aren't block constructs. The low-level parser entry points are simplified and renamed to parse-one, parse-all, and parse-file.
JeffBezanson
added a commit
that referenced
this issue
Jan 8, 2019
This gives better location info inside `:toplevel` expressions and for REPL inputs that aren't block constructs. The low-level parser entry points are simplified and renamed to parse-one, parse-all, and parse-file.
JeffBezanson
added a commit
that referenced
this issue
Jan 8, 2019
This gives better location info inside `:toplevel` expressions and for REPL inputs that aren't block constructs. The low-level parser entry points are simplified and renamed to parse-one, parse-all, and parse-file.
JeffBezanson
added a commit
that referenced
this issue
Jan 8, 2019
This gives better location info inside `:toplevel` expressions and for REPL inputs that aren't block constructs. The low-level parser entry points are simplified and renamed to parse-one, parse-all, and parse-file.
JeffBezanson
added a commit
that referenced
this issue
Jan 9, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
LineNumber
nodes can be used to add line numbers to a:block
expression, but are ignored in:toplevel
expressions:This seems like it makes it unnecessarily hard to add a line number when evaluating an arbitrary expression, because you can't put toplevel-only expressions (e.g.
module
orstruct
) inside:block
expressions.(This came up in addressing JuliaLang/SoftGlobalScope.jl#3.)
The text was updated successfully, but these errors were encountered: