End-to-End Performance about python-indent

[kbrose]

Some thoughts:

Maybe we could try and use some cacheing? E.g., if only code on line > 150 has been changed, then the openBracketStack as it was for lines 0-150 will still be the same the next time you press Enter, so if we had cached the value of openBracketStack (and I guess all the other stateful variables, e.g. are we in a string, is it a triple quoted string, etc.) as it was on line 150, then we could start processing only from there down.

This might combine well with actually having it run more often than just on "enter" events, i.e. every x milliseconds (where x could be configurable), so that you can keep your cache more up to date.

[kbrose]

The open bracket stack is theoretically unbounded in size, but would take _a lot_ of open brackets in order to even break into the megabytes. Still, something to think about.

[DSpeckhals]

Closing...if the need presents itself, we'll take care of it.