syntax tree diffing is used in many places in IDE. even for things like VB auto commit which will run on UI thread.(but cancellable)
like incremental parsing perf test in compiler perf test, we should have tree diffing perf tests for unrelated tree (no green node sharing) and related tree (green node sharing most likely due to incremental parsing)
...
also, we have 2 different diffing mechanism. one for most of IDE uses (fast but less accurate by using green node comparison) and more accurate one (but uses red node) used by Enc.
it would be nice if we have perf tests for both of cases since it is used heavily by IDE.
syntax tree diffing is used in many places in IDE. even for things like VB auto commit which will run on UI thread.(but cancellable)
like incremental parsing perf test in compiler perf test, we should have tree diffing perf tests for unrelated tree (no green node sharing) and related tree (green node sharing most likely due to incremental parsing)
...
also, we have 2 different diffing mechanism. one for most of IDE uses (fast but less accurate by using green node comparison) and more accurate one (but uses red node) used by Enc.
it would be nice if we have perf tests for both of cases since it is used heavily by IDE.