[nem-en] Integration issues

[Igor Tkachev]

Hi All,

We are facing a few issues working on the integration project which can
not be solved by ourselves. Here they are:

1. When the compiler creates the typed tree, it also optimizes result
   and we lose some information we need for completion, tips,
   navigation, etc. In this mode we need compiler to create the typed
   tree only. 

   I think we will need the same for debugging.

2. While the user is changing a method body, locations of methods
   below are being changed as well. Those changes are made most
   frequently and if we call compile every time, it will kill
   performance. 
   
   We could optimize this if we corrected locations of the methods
   bellow the current position. But, unfortunately, locations are
   read-only.

   So, the question is - can we make it mutable?

3. I wrote about this issue a couple of weeks ago, but I did get any
   answer. I guess, I was not clear enough.

   The idea is to keep relations between PExpr and TExpr objects.
   Every time a TExpr object is created, it should get a reference to
   a PExpr object which was a cause of the TExpr object creation.

   This will let us get precise location for the TExpr objects and
   optimize some algorithms.

   
Michal, Kamil, you are only our hope :)
   
-- 
Best regards,
Igor
mailto:it at rsdn.ru