At the moment there's no caching mechanism... I was thinking about adding caching, based on objects' references.
However, I don't know whether this would make sense: when you write in the editor the AST model changes many times. Probably though Xtext should only rebuild the parts that really changed and the objects' identifiers should not change.
I might try to add caching in the future, and it should not be too hard to implement (but first I'd like to port Xsemantics to Xtext 2.4.2).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Of course, updating to Xtext 2.4.2 is certainly more important.
Still: The type system is created on the fly when needed, that is, it is not a singleton, is it? So, caching information there would be similar to caching in the scope provider, wouldn't it?
As a workaround: could I use Gamma (G) as a kind of cache?
Regards,
Jens
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm wondering whether the result of a rule, in particular of an auxiliary function, is cached? E.g., I have an auxiliary functions
which are quite expensive.
Regards,
Jens
At the moment there's no caching mechanism... I was thinking about adding caching, based on objects' references.
However, I don't know whether this would make sense: when you write in the editor the AST model changes many times. Probably though Xtext should only rebuild the parts that really changed and the objects' identifiers should not change.
I might try to add caching in the future, and it should not be too hard to implement (but first I'd like to port Xsemantics to Xtext 2.4.2).
Of course, updating to Xtext 2.4.2 is certainly more important.
Still: The type system is created on the fly when needed, that is, it is not a singleton, is it? So, caching information there would be similar to caching in the scope provider, wouldn't it?
As a workaround: could I use Gamma (G) as a kind of cache?
Regards,
Jens