Claire Foster

I'd forgotten about this issue, but it's now fixed in JuliaLowering.jl! From the tests, we now get: ```julia LoweringError: struct X{S,T} X() = new{A}() # └────┘ ── too few type...

Maybe one day we can refer to multiple source ranges (https://github.com/c42f/JuliaLowering.jl/issues/8) and have something even better like ```julia LoweringError: struct X{S,T} # └─1──┘ X() = new{A}() # └┈2┈┈┘ ── Too...

Yes, the tokenizer assumes `!=` should always be parsed as a token if it's present, taking precedence over a `!` on the end of an identifier. I'm not sure `x!=1`...

Heya, we just moved JuliaSyntax into Base in https://github.com/JuliaLang/julia/pull/59870 - if you want to re-propose this PR over there, I've created a branch https://github.com/JuliaLang/JuliaSyntax.jl/tree/pr-for-Base/404 to make this easier. To make...

Here's the parts which are reusable, in principle: * `ParseStream` and its associated types and generic functions `emit() / bump()` in `parse_stream.jl` - the majority of this is general and...

This looks like a limitation (or design decision) of postgres itself so you should split these into separate statements.

I want to avoid writing a lot of hand-engineered error messages for special cases which is why I haven't pushed very hard on fixing this specific issue (sorry!) But I...

Having mentioned this elsewhere I thought I'd expand just a little on the design we were discussing when this was originally written. Distinct `Kind`s are only really useful to the...

So, I think we want to emit a warning for this and eventually deprecate it. I had a quick go at starting to implement it in `Expr` conversion but that...

The error messages for this kind of thing did change recently in #397 to improve the highlighted range but... that change does rather clash with this particular type of error....