Loading...

XML

Word

Printable

Type: Sub-task
Resolution: Won't Fix
Priority: P3
Fix Version/s: None
Affects Version/s: 8
Component/s: tools
Labels:
- noreg-cleanup
- type-annotations

Introduced In Version:

8

Issue	Fix Version	Assignee	Priority	Status	Resolution	Resolved In Build
JDK-8046264	9	Eric Mccorkle	P3	Resolved	Fixed	b19

Presently, the location and type path information for a type annotation is determined by resolveFrame, which is called late in the pipeline, after repeating annotations handling in particular. This is a source of problems, not the least of which is that the position of some annotations is not updated until after repeating annotations has built containers.

An alternative is to build location information during attribution, attach it to the JCAnnotation tree node, and use the information when attaching annotations to their respective symbols.

backported by

JDK-8046264 Determine location for type annotations earlier in compiler pipeline

Resolved

blocks

JDK-8042060 Type parameter annotations don't work with multiple type parameters

Closed

is blocked by

JDK-8033004 Make base TypeAnnotationPosition data immutable, create better methods for obtaining base TypeAnnotationPositions

Closed

JDK-8038263 Refactor annotation handling after actualEnterAnnotations

Closed

JDK-8036142 Remove redundant call to annotateTypeLater with null Symbol

Closed

relates to

JDK-8056021 checkin for JDK-8027262 breaks Checker Framework

Closed

(1 relates to)

Assignee:: Eric Mccorkle

Reporter:: Eric Mccorkle

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2013-10-24 10:16

Updated:: 2024-10-09 13:05

Resolved:: 2014-06-16 10:00

Details

Backports

Description

Attachments

Issue Links

Activity

People

Dates