AnnotationModel uses both fAnnotations and getAnnotationMap() #19
Assignees
Milestone
Comments
iloveeclipse
added a commit
to iloveeclipse/eclipse.platform.text
that referenced
this issue
May 6, 2022
(Fixes eclipse-platform#19) AnnotationModel.fAnnotations is deprecated and getAnnotationMap() should be used instead. However I still see the code that uses AnnotationModel.fAnnotations inside AnnotationModel, even together with the getAnnotationMap(). This should be fixed as precondition to fix of inefficient map iterations inside same class. eclipse-platform#19
This was referenced May 6, 2022
iloveeclipse
added a commit
to iloveeclipse/eclipse.platform.text
that referenced
this issue
May 6, 2022
(Fixes eclipse-platform#19) AnnotationModel.fAnnotations is deprecated and getAnnotationMap() should be used instead. However I still see the code that uses AnnotationModel.fAnnotations inside AnnotationModel, even together with the getAnnotationMap(). This should be fixed as precondition to fix of inefficient map iterations inside same class. eclipse-platform#19
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
AnnotationModel.fAnnotationsis deprecated andgetAnnotationMap()should be used instead.However I still see the code that uses
AnnotationModel.fAnnotationsinsideAnnotationModel, even together with thegetAnnotationMap(). This should be fixed as precondition to fix of inefficient map iterations inside same class.The text was updated successfully, but these errors were encountered: