Community
Participate
Working Groups
When having complex result computations in a method it would be good to mark a method as "cached", similar to "create", but without the need to create a result object. This could look like this: def cached computeSomething () { }
This feature was already discusses in the past and we decided to not built some caching mechanism into the language. Xtend allows to define fields which in turn allow to inject / use own caching services with fine grain control on the cache-lifecycle / -semantics / -implementation on the user side. Please feel free to reopen if I missed your point.
In this case the Xtend library should provide a useful set of caching extensions, since it is likely that users want to enable field based cachings bound to the lifecycle of the class instance. If the user wants to implement own semantics, he would be free to add his own implementation, of course. But I guess the at least 90% case is per-instance, like the create method scope.
I don't think that such a caching extension is in the scope of the xbase lib or xtend lib. Therefore I'd like to close this ticket as won't fix. Any objections?
Agree.
Closing all bugs that were set to RESOLVED before Neon.0
