Eclipse Community Forums: TMF (Xtext) » Xbase: proposals of non-final variables in lambdas

Help

Home

Home » Modeling » TMF (Xtext) » Xbase: proposals of non-final variables in lambdas

Show: Today's Messages :: Show Polls :: Message Navigator

Xbase: proposals of non-final variables in lambdas [message #1403837]

Mon, 28 July 2014 08:22

Lorenzo Bettini

Messages: 1812
Registered: July 2009
Location: Firenze, Italy

Senior Member

Hi

If I remember correctly (at least, I have Junit tests that now fail)
before Xtext 2.6, the default Xbase proposal provider did NOT propose
writable variables within a lambda expression's body

For instance, in Xtend

def m(int i) {
var j = 0
newArrayList().forEach[
println(<--- proposals
]
}

proposals contained "i" but not "j" (since "cannot refer to non-final
variable inside a lambda expression").

This is not the case anymore in Xbase 2.6 (and this is visible also in
Xtend): "j" is proposed as well...

Is that intentional?
I think that before that was implicitly implemented by the deprecated
XbaseScopeProvider, which was used only in the content assist (i.e., not
for type checking and validation).

cheers
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book

HOME: http://www.lorenzobettini.it
TDD Book: https://leanpub.com/tdd-buildautomation-ci
Xtext Book: https://www.packtpub.com/application-development/implementing-domain-specific-languages-xtext-and-xtend-second-edition

Report message to a moderator

Previous Topic:	[SOLVED] UnsupportedOperationException on enum
Next Topic:	Inherit properties of supertype

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 21:14:18 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter