Hello Small question when I use `getSymbolsWithAnnotation` w

Question

Hello Small question when I use `getSymbolsWithAnnotation` with multiple deferring Annotation for a Class target Is it suppose to pick up only the first

Matthias Geisler · Answer

To make it a bit clearer what I mean

Matthias Geisler · Answer

In this case only ` MockCommon` is the first I extract via `getSymbolsWithAnnotation` and surprisingly it also contains ` Mock`and ` MockShared`

Matthias Geisler · Answer

Is that intentional or shall I file a bug report

Grégory Lureau · Answer

getSymbolsWithAnnotation give you all symbols annotated with MockCommon Once you have the symbol you can get everything that belongs to it like all the annotations of this symbol it s not related to the resolver method you used initially to get the symbol

Matthias Geisler · Answer

But why it takes then a parameter annotationName

Matthias Geisler · Answer

Also the doc state Get all symbols with specified annotation

Grégory Lureau · Answer

gt getSymbolsWithAnnotation give you all symbols annotated with MockCommon You cannot find your class `Platform` without giving the annotation name of MockCommon Let s say you also annotate another class like `Shared` with MockCommon then getSymbolsWithAnnotation will return Platform Shared

Grégory Lureau · Answer

And Platform will still have 3 annotations and Shared only one

Matthias Geisler · Answer

I think you do not get me here The Sequence which is returned from `getSymbolsWithAnnotation` when I call it with the name for example of MockCommon will contain in the example above also the Annotated for Mock and MockShared That would not be that bad but if call it again for Mock or MockShared those Annotated are not resolved

Matthias Geisler · Answer

There for the pictures

Matthias Geisler · Answer

Where the Annotation sits does not matter in this case

Grégory Lureau · Answer

Ah ok sorry for the misunderstanding

Matthias Geisler · Answer

No problem but is it clear now

efemoney · Answer

< Matthias Geisler> from the screenshot you shared get symbols with MockCommon will return only `Platform`

efemoney · Answer

But then you proceed to read all annotations of Platform amp print them and obviously Platform is annotated with ALL 3 annotations

efemoney · Answer

Where is the problem here

efemoney · Answer

This is not surprising behavior Infact I am more surprised you are expecting differently

Matthias Geisler · Answer

Did you read the entire Thread

efemoney · Answer

I did but I wanted to address just the code that you shared firstly Just so that I understand you better are you saying that calling get symbols annotated with Mock amp MockShared returns empty

Matthias Geisler · Answer

Yes

Matthias Geisler · Answer

But common contains the Annotated for them in its sequence

efemoney · Answer

Are you calling getSymbolsWithAnnotation multiple times in the same round

Matthias Geisler · Answer

yes

Matthias Geisler · Answer

currently 4times

efemoney · Answer

Cool thumbsup skin tone 3 I think you should file a bug then with a reproducer It should just work

Matthias Geisler · Answer

Sure but I hoped < Jiaxiang> or < Ting Yuan Huang> pick it up maybe they think it should work the other way

efemoney · Answer

I am unable to reproduce this with latest ksp thinking face Is there something your project does differently from this

efemoney · Answer

note the subsequent printed headers are from the 2nd round and like KSP mentions in the javadoc for getSymbolsWithAnnotation only deferred symbols amp new files are processed

Matthias Geisler · Answer

That is interesting I am sitting still on 1 6 10 but there was nothing mentioned in the release notes about changes that specific method

efemoney · Answer

Ksp api hasnt changed from then the 1 0 5 part

Matthias Geisler · Answer

Yeah but you never know

Matthias Geisler · Answer

And the annotations are with ``` Retention AnnotationRetention SOURCE Target AnnotationTarget CLASS ```

Matthias Geisler · Answer

But it should not have any effect since I was able to reproduces when I removed the target

efemoney · Answer

I switched to 1 6 10 1 0 4 and got same results

Matthias Geisler · Answer

Super wired after poking stuff around then reset it to the starting code git checkout is always the best now I get the same result

Matthias Geisler · Answer

Super wired

Matthias Geisler · Answer

And < efemoney> thx that you invested time btw

efemoney · Answer

Awesome Glad you got it working Sometimes you just have to turn it off and on again sweat smile

efemoney · Answer

If you are ever able to reproduce it I would suggest opening an issue At a minimum you ll understand why it happens In the best case you ll have discovered a potential bug in ksp that can be fixed for someone else

Matthias Geisler · Answer

Let s hope that never happens again

Jiaxiang · Answer

It is quite a long thread good to see that it eventually works sometimes there could also be issues with compiler version feel free to file a bug if you encountered it again slightly smiling face