Why aren't all of the Ks* e.g. KS_Visitor functions documented with kdoc? Some things are and others aren't, in my opinion this makes it really ambiguous especially when you want to extend KsVisitor where some of the function are similarly named, making it very hard to know the precise use of each.
Save the date for the upcoming Kotlin 2021 Premier Online Event videos - kotl.in/Kotlin-Event-2021
Why aren't all of the Ks* e.g. KS_Visitor functions documented with kdoc? Some things are and others aren't, in my opinion this makes it really ambiguous especially when you want to extend KsVisitor where some of the function are similarly named, making it very hard to know the precise use of each.
Why not just introduce static reflection as part of the language?
What a Kerbal Space Program reference
Needs more boosters
Thank you
thank'ou
Why API is like fun getAllFiles? It looks like val allFiles would be a better fit
My 2c: it could be because the operation is not idempotent (in theory), and it is not exposing a state so much as a behaviour.
I guess KSP is like AspectJ in Java?