Mercerenies
commented
1 year ago I've taken the time to review the warnings we currently get in Godot, and to be quite frank, they're a bit silly. There are currently (as of 531f883) 11 warnings.
- One is an "unused variable" in a loop that, to be honest, is a fair point. We could (and probably will, at some point) fix that.
- Two are "ternary results are not mutually compatible". One of these is a
condthat didn't get optimized quite to my satisfaction, but the other is a ternary that, by design, returns a 2- or 3- dimensional vector. If we chose to fix the latter, it would just be a 'warning ignore' directive. - The other eight are "function declaration conflicts with variable of the same name", which is, to be quite blunt, just absurd. These are for names like
Colorwhich can be used as a value-like object (Color.red) or as a function (Color(0, 0, 0)). This is literally built-in Godot behavior that I'm just thinly wrapping. But when I do it, it's a warning. I cannot fix this without making my system less like the Godot runtime.
We'd like GDLisp.gd to open in Godot without any warnings. This will probably just consist of throwing up a bunch of comments telling the Godot warning engine to cool it.
Currently (#58), we can't even open GDLisp.gd in Godot, so #58 is blocking this issue.