Lilith Orion Hafner
Lilith Orion Hafner
It would be lovely to have a public way of accessing `sn.data.source.code[range(sn)]` for some `sn::SyntaxNode`. The function name `AbstractString` is tempting, but perhaps a better one would be `source`?
This came up at https://github.com/JuliaLang/julia/pull/53119 @LilithHafnerBot bisect() ```julia using JuliaSyntax JuliaSyntax.parse("a.[1]") ```
WIP c.f. https://github.com/JuliaLang/julia/issues/52784 There will also need to be changes to eval, though I think lowering already supports this.
```julia-repl julia> import a, b, c=d e, f, g, h ERROR: ParseError: # Error @ REPL[50]:1:17 import a, b, c=d e, f, g, h # └─────────┘ ── extra tokens after...
"even Claire said so" –@c424 These don't all need different kinds: ``` ... "⥺" "⭇" "⭈" "⭉" "⭊" "⭋" "⭌" "←" "→" "⇜" "⇝" "↜" "↝" "↩" "↪" ... ```
I'm missing a `)`, but the new error message doesn't make that as clear as the old one. Julia 1.0 ```julia julia> quote const $(esc(Symbol(name)) = 4 export $(esc(Symbol(name)) end...
I ran into this in the wild when I typoed a ` x = [rand() ? .9 ? rand(1:1000) : missing for _ in 1:100]; ERROR: ParseError: # Error @...
flisp ```julia julia> f(a, b, c d, e) ERROR: syntax: missing comma or ) in argument list ``` JuliaSyntax ```julia julia> f(a, b, c d, e) ERROR: ParseError: # Error...
I think `export (foo)` should also not be allowed (hopefully nobody uses it)
I would like to be able to ask questions like "find all occurrences in General and Base of a string literal immediately preceding a function declaration in a block environment...