Bug 422784 - [1.8] recovery of type annotations in the presence of syntax errors
Summary: [1.8] recovery of type annotations in the presence of syntax errors
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.3   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-28 12:04 EST by Stephan Herrmann CLA
Modified: 2022-06-09 14:05 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stephan Herrmann CLA 2013-11-28 12:04:40 EST
The fix in bug 414038 comment 10 excludes type annotations from recovery.

A previous patch in bug 414038 comment 2 only fixed the malformed AST problem without excluding type annotations from recovery, but this fix likely is incomplete.

At some moment of leisure we should revive and polish that patch.
Comment 1 Srikanth Sankaran CLA 2013-12-18 20:44:53 EST
I am deferring this to 4.4. 

The dominant usage for type annotations is going to be marker interfaces
that implement type qualifiers - these cannot be broken as much as normal
annotations and so recovery is not that crucial.

We will pull this up to Java 8 if time permits.
Comment 2 Srikanth Sankaran CLA 2013-12-18 20:48:44 EST
Just a note that where type annotations occur in SE7 locations, they are
recovered and attached as much as declaration annotations. From the parser's
point of view these are SE7 annotations.

The current recovery system, tracks "pending annotations" annotations and
attached them to elements as they get recovered - these are all SE7 annotatable
elements.
Comment 3 Manoj N Palat CLA 2018-05-17 03:25:15 EDT
bulk move out of 4.8
Comment 4 Eclipse Genie CLA 2022-06-09 14:05:09 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.