Reduce number of temporary variables emitted by code generation

[aspizu]

Currently, for each function call, one temporary variable is emitted. This affects the load time of the project in Turbowarp which hinders the dev workflow.

[Bituvo]

Can you elaborate on that? What is a "temporary variable" in this context?

[aspizu]

Each function call emits a variable named __callsiteN__ where N is a integer. It's set to the __funcName_return__ variable after calling the function procedure.

[faretek1]

Callsite vars only really need to be made if the function being called is used twice in the same 'line' of gs code/'callsite', no?

Surely if a function is only used once for the callsite, you can directly grab from the function return variables? (just wondering what is making this a confusing problem and im probably missing something)

[faretek1]

However, if that function is used within another function which is also used for that same callsite, things become complicated