Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 401448 - [1.8][spec] complete definition of assignment context
Summary: [1.8][spec] complete definition of assignment context
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.3   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: BETA J8   Edit
Assignee: Stephan Herrmann CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 401003
  Show dependency tree
 
Reported: 2013-02-21 13:07 EST by Stephan Herrmann CLA
Modified: 2013-12-17 23:03 EST (History)
1 user (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-02-21 13:07:43 EST
JSR 355 0.6.1 uses the phrase "assignment or invocation contexts" to denote
situations where an expression may be a poly expression.

The introduction of section 5 has an informal discussion 
where item 2 bullet 1 starts:

  "Assignment contexts (including return statements, etc.) are supported" 

which implies that the term "assignment context" is used loosely, to include
many more syntactic constructs. I cannot find a precise definition for this.

This needs clarification, for which I could envision two alternatives:
(a) give a complete positive list of syntactic contexts
(b) explicitly extend the notion to all expression contexts *except for*
    statement contexts.
Comment 1 Stephan Herrmann CLA 2013-12-12 18:17:56 EST
A fix had been promised in http://mail.openjdk.java.net/pipermail/lambda-spec-experts/2013-February/000235.html but still in 0.7.0 I can't find a real answer.

By including return statements into the list, most obvious cases are already covered, but still a full list would be helpful.
Comment 2 Srikanth Sankaran CLA 2013-12-17 23:03:30 EST
This has been acknowledged as a gap in JLS and a bug has been raised by the
spec lead: https://bugs.openjdk.java.net/browse/JDK-8030361. 

So no further action is required from Eclipse side in this ticket.