Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 362725 - [Xtend 2.1] can no longer do null check on closure parameter
Summary: [Xtend 2.1] can no longer do null check on closure parameter
Status: CLOSED FIXED
Alias: None
Product: TMF
Classification: Modeling
Component: Xtext (show other bugs)
Version: unspecified   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: M4   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-02 17:04 EDT by Edwin Park CLA
Modified: 2017-09-19 17:11 EDT (History)
2 users (show)

See Also:
sven.efftinge: juno+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Edwin Park CLA 2011-11-02 17:04:20 EDT
Build Identifier: 20110916-0149

I have a function that takes a closure argument and then checks to see if it is null:

def String function(Expression e, (String) => String closure) {
  ...
  if (closure != null)
  ...
}

The ==, != comparisons used to work in Xtext 2, but with 2.1 they now give me "Could not resolve reference to JVMIdentifiableElement '!='" errors in the Xtend editor.


Reproducible: Always

Steps to Reproduce:
1. Create an Xtend function with a closure parameter
2. Attempt to check if that closure parameter is null (closure == null, closure != null)
3. Note that the Xtend editor will give an error and the corresponding Java class will not be generated
Comment 1 Sebastian Zarnekow CLA 2011-11-21 17:08:25 EST
Pushed to master.
Comment 2 Karsten Thoms CLA 2017-09-19 16:59:31 EDT
Closing all bugs that were set to RESOLVED before Neon.0
Comment 3 Karsten Thoms CLA 2017-09-19 17:11:01 EDT
Closing all bugs that were set to RESOLVED before Neon.0