Closed lbtrace closed 1 year ago
Seems like a bug in the grammar to me
Hi @KvanTTT what do you think about this issue?
I think the same: it looks like a bug in the grammar.
Thanks for replay @belyaev-mikhail @KvanTTT
So, maybe we should modify constructorInvocation
like this:
constructorInvocation
: userType NL* valueArguments
;
Do you know who can determine these things?
Yeah, that's definitely a bug, thanks for bringing it to our attention! We'll do our best to fix it in the spec 1.9 release.
Hi @lbtrace, Kotlin Studio is not using KotlinParser.g4
. In kotlinx.ast, we have own copy of this file. But sadly, I still have to fix the build system. If you can use a local build version for kotlinx.ast, you can fix it locally:
constructorInvocation
: userType NL* valueArguments
;
Yes, I will fix it locally, thanks for your suggestion
Fixed in a94315649ae44453d6e0a639d4de1a586c8176e2, soon to be released in version 1.9
Hi, I am Android developer from China, I using ANTLR4(using KotlinParser.g4 version v1.8) as kotlin AST library. And i find some confusion about "constructorInvocation".
userType
andvalueArguments
NOT containsNL*