The new `addNewImplicitReceivers` signature is ver...
# compiler
y
The new
addNewImplicitReceivers
signature is very hard to use. In IR, it results in either an error call (which is fine, I can work with that) or a seemingly-undetectable reference to a real extension parameter but with the wrong type (i.e. it might refer to the extension param of a local
apply {}
). The latter I really can't detect easily. DataFrame gets lucky because the calls one may ever want to make on the new implicit receiver are calls to fir generated properties. In my case, I have real properties and such I want to access on it. If somehow it could always be an error call, that'd be great. Ideally, I wish it'd actually keep the
origin
and maybe even provide a reference to the function call that resulted in this new implicit receiver (more on that in the post above)
I've found somewhat of a work around. The
receiverParameter
I create now has an inappropriate containing callable symbol, and this seems to force it to always result in an error call.
d
I wrote many times that this extension was never expected to be used elsewhere outside data frame, so it wasn't properly designed for any other usecase.