Prevent compilation when local variable limit is hit

[Zamiell]

Today, in Discord, we discussed the possibility of TSTL taking extra steps to handle the case of a TSTL program with over 200 local variables.

Right now, it sounds like Perry just wants to keep things as is, given that there are tradeoffs with either option.

However, everyone can agree that run-time errors are terrible - the whole point of using TSTL in the first place is to stop run-time errors. With that in mind, can we make TSTL keep a counter of the current scope's local variables, and then refuse to compile (or throw a warning) if the counter reaches 200? (Or maybe even 190, to be a little on the safe side.)

This would give the end-user the chance to refactor their program long before running into any issues in production!

[Perryvw]

What should the threshold be? Is it the same for every lua target/version?
I guess we would also have to be able to disable it in case there is some weird patched target.

[Zamiell]

Well, isn't it almost always 200?

See: https://github.com/lua/lua/blob/master/lparser.c#L35
And: https://stackoverflow.com/questions/66511018/lua-how-many-variables-a-local-can-hold

So use 200 * 0.95 as a default, and maybe add it as a compiler option to adjust at will, with a special value of 0 effectively disabling the feature.