<@U4UGS5FC7> <@U4TNC7C4B> I ran into some weirdnes...
# arrow-metaa
amanda.hinchman-dominguez
11/13/2019, 5:50 PM@raulraja @bloder I ran into some weirdness attempting to create a default element scope for
KtNullableTyper
raulraja
11/13/2019, 6:11 PMreplied on there I think we need KtTypeReference and KtTypeElement
👍 1
raulraja
11/13/2019, 6:11 PMas those are the ones that show up on a type in user code being KtTypeReference the primary one
raulraja
11/13/2019, 6:12 PMfor example a function return type, receiver etc are all KtTypeReference
a
amanda.hinchman-dominguez
11/13/2019, 6:15 PMYes, we'll add that to the list
amanda.hinchman-dominguez
11/13/2019, 6:18 PMwe already had
KtTypeElementamanda.hinchman-dominguez
11/13/2019, 6:18 PMRight now, our current strategy is to basically go through what psi elements have not been covered that's already in ElementScope, for sure
amanda.hinchman-dominguez
11/13/2019, 6:19 PMAlso, right right now, try to merge in all the open ones we have right now haha
amanda.hinchman-dominguez
11/13/2019, 6:19 PMupdating the branches were a little hectic 😄
amanda.hinchman-dominguez
11/13/2019, 6:20 PM@raulraja should I just remove trying to get a
delegateElementScopet
tschuchort
11/13/2019, 6:54 PMBtw TypeReference ist called TypeMirror in the Java annotation processing API. While reference is more clear, it is worth considering changing the name for familiarity with the existing annotation processing API or explaining this relationship in the docs.
➕ 1
a
amanda.hinchman-dominguez
11/13/2019, 6:55 PMHmmm... that's a really good point - but I don't think we're working with annotations for using the quote system. I might be wrong about this - @raulraja what do you think?
r
raulraja
11/13/2019, 6:56 PMwe should explain the relationship in the docs but the current approach is to follow the same naming conventions as the KtElements except the Kt part
👍 2
a
amanda.hinchman-dominguez
11/13/2019, 6:56 PMI can definitely add that in there in a second