Closed draivin closed 10 years ago
Hmm, thanks for catching that. It seems that only parts of the compiler interpret a null
TextChangeRange
as a hint to re-process the whole file. For now, changing to the pedestrian alternative, explicitly marking a range covering the old and new contents.
Calling update repeatedly will cause the program to stop returning useful information.
Test case:
produces