Replaying a macro while it is being recorded hangs the page

[veluca93]

Replaying a macro while it is being recorded hangs the page

[nightwing]

Currently we rely on maximum call stack size exceptions, so @A repeats the macro 512 times.

Unfortunately performance of the extension on v6 is worse than v5, so repeating macro 500 times takes about a minute.
Aside from fixing performance issue, should we also always prevent macro recursion, or can that be useful in some situations and keeping behavior from https://codemirror.net/5/demo/vim.html is ok?

[veluca93]

I admit I didn't expect that repeating the macro 500 times would lock up the page this badly :-)

I can't at the moment think of a usecase where macro recursion would be useful, but IMO it's best to stick to the vim behaviour if possible (i e. Allow recursion)

[Opisek]

For the case of tail-recursion, so playing the macro at the end of recording, we could avoid using a call stack entirely. This would also extend to mutually-recursive recordings like qa@bqqb@aq.

If the recursive call takes place in the middle of a recording then it's down to classic optimizations.