On 03/28/2014 07:23 PM, Victor Rubezhny wrote:
What is the point of resolving bindings each time we need to create an
AST when reconcile? (It happens for almost each character typed in by
a user or the selection is changed in the editor).
Could it be implemented that way to save heap space? Did you try to
measure memory usage with lazy resolution vs full parsing?
If it is the reason, then it seems to me that memory isn't much of a
end-user problem nowadays and that as long as it doesn't cause
OutOfMemory to users, it's probably worth increasing the memory usage to
improve reactivity and speed.
I'm getting the AST produced almost 8 times faster and no more
StackOverflowErrors in "Semantic Highlighting Job", "Requesting
JavaScript AST from selection" and "Decoration Calculation" Jobs.
That sounds like a great result!
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
_______________________________________________
wtp-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/wtp-dev
