Hi, here is the latest KSP release. Please note that we are pretty close to beta stage. In beta stage we want to avoid making API changes, if you have any changes you want to see in terms APIs, now is still a good time. This release is a pretty long one, please refer to the release note on Github for full list of changes in this release. Major breaking changes: • switch to 

Sequence

 for a bunch of APIs ◦ Some of the API return type has been changed from 

Collection

 or 

List

 to 

Sequence

, which will allow performance improvement if you use case involved early termination. ◦ Note that because 

Sequence

 is lazily evaluated, it requires a terminal operation to make actual compute happen. Please check you uses around the impacted APIs to see if they have a terminal operation. Most common use case is 

Collection.map{}

 which will iterate through the collection by itself, but is non-terminal for 

Sequence

 and should be companied with 

toList()

 or replaced with 

forEach

◦ For the whole list of APIs impacted by this change, please refer to this commit. • Origin for KS symbols from binaries is now split into 

KOTLIN_LIB

 and 

JAVA_LIB

.

One api i have on my mind if the ability to check if a property has a backing field. I've been meaning to add it but didn't have much time these days

I can add an issue for that

i started working on this

In

resolveUtil.kt

,

getter != null -> false

looks weird to me; A backing field can be used in a getter, right?

For room, we need to know to decide whether that property should be saved into a database column or not. While searching usages of the internal api on kotline source code, i noticed kotline serialization does the same

I'm trying to see if there's some way to infer the backing field but so far haven't found anything

That seems feasible to me. Just a minor change is needed to get the jvm name i guess but i can take it from your patch. Meanwhile, we should probably double check with JB on why that method does not really work

Not having to consider jvm name sounds a great relief :-) As for override / inheritance, since the API is on KSPropertyDeclaration, which is always the place where it is defined, we probably don't need to check overridden property?

thats what i'm trying to figure out but the API in kotlin compiler looks for overrides, though only when it is fake:

fun PropertyDescriptor.hasBackingField(bindingContext: BindingContext?): Boolean = when {
    kind == CallableMemberDescriptor.Kind.FAKE_OVERRIDE -> overriddenDescriptors.any { it.hasBackingField(bindingContext) }

That doesn't seem to applicable in our case, or we have something to fix in getAllProperties

yea i think we don't return them