He1pa
He1pa
> Hi @He1pa! Thanks for the detailed response. Since this is an LFX issue, I thought the same would be frozen for contributors until the mentees are officially announced, and...
some advices: + I think you should sort out all the syntax errors first (you can search for `struct_span_error`) and do some classification. For example, what can be fixed, code...
> > some advices: > > > > * I think you should sort out all the syntax errors first (you can search for `struct_span_error`) and do some classification. For...
> > I think this should be done through parser specific error generation expression instead of passing code snippets to LSP and then handing them over to LSP for judgment....
good idea. I will impl this feature later
I'm not sure if all fixes can be expressed just in suggestions. and whether there is enough information to generate suggestions when the error is generated. Like I said before,...
> Need some help with this on how to implement quick fixes for these kind of errors: cc @Peefy @He1pa > > * https://github.com/kcl-lang/kcl/blob/26b1b17c6a94d2239153a3a59256a8c5b2ebdff7/kclvm/parser/src/lexer/mod.rs#L327-L330 > > Reproduced by: > >...
for `z = func([x: ]a, [y: ]y = 1, [z: ]z = 2)` , `[y: ]` and `[z: ]` are not needed. I perfer `z = func([x: ]a, y =...
> I think there is a small problem here that when a function parameter is input with a literal constant, there is actually no parameter symbol here, right? Can you...