Vector line draw functions

[Leo-MathGuy]

Screen.deg_line(x0, y0, degrees, magnitude) -> Line with origin, degrees, and magnitude
Screen.rad_line(x0, y0, radians, magnitude) -> Line with origin, radians, and magnitude

Partially fixes #35 but wont be fully fixed until lists get added

This might be useful for game design, animations, and if someone decides to recreate a ti-84 in mindustry

Also fixes a small bug in sorted config test file

[Lonami]

pyndustri.pyi should be updated to explain what these do.

[Leo-MathGuy]

Ok going to do that

[Leo-MathGuy]

Done

[Lonami]

Thanks. These functions only work with literals, and won't work with runtime variable values, right? So I'm wondering how useful are they, in practice?

[Leo-MathGuy]

Hmmm, I think its like that because it does the trig calculations during compilation of the program.
Is there a was in ast to get the value of a? (like *a in C to get the value of the variable from pointer a)

Like
`a = 50
b = 50

for i in range(0, 360):
Screen.deg_line(a, b, i, 10)

Screen.flush()`

Because the trig calculations are done during compilation, it tries to use "a" as the x0, not the value of a.

[Leo-MathGuy]

Because of that its useless for now

[Leo-MathGuy]

Like if you do a/2 it tries to use "__pyc_tmp_3" (string) as x0

[Leo-MathGuy]

@Lonami Is there a way in ast to check if a variable is a literal or variable name? And how to get the value of that variable?

[Lonami]

The value of variables is calculated while Mindustry runs the program. You cannot get it from the compiler, because the value may come from a sensor (such as reading how many items a container has).

The only way is to do the calculations inside Mindustry too.

Constant folding, which is in a way what you did here, is definitely useful and could be applied thorough the compiler (at the cost of increased complexity). I'm not sure we should start doing that until we figure out a clean design, but this is a whole difḟerent topic entirely.