Godot typing warning
Godot devs are warning against non‑static typing to avoid performance hits and degraded autocomplete — a reminder to prefer static types in GDScript for bigger projects. (x.com).
Godot’s official documentation says typed GDScript emits optimized opcodes when operand and argument types are known at compile time, and that static types improve editor autocompletion. (docs.godotengine.org) The engine exposes enforcement knobs — the Project Settings Debug → GDScript “UNTYPED_DECLARATION” warning can be set to WARN or ERROR, and the editor option Text Editor → Completion → Add Type Hints can auto-insert annotations (noted in community guides and tooling write-ups). (allenwp.com) Community benchmarks report concrete gains: one independent test measured up to ~47.04% faster Vector2 math in release builds when using static types, and academic/undergraduate analyses also document lower runtime overhead for statically-typed GDScript. (bodenmchale.com) Godot community posts and blog authors recommend turning on untyped-declaration warnings early because converting a large existing project to full static typing is often time-consuming; several tutorials show migration steps like enabling safe-line visualization and adding class_name to custom classes. (forum.godotengine.org) The docs also note future GDScript optimizations such as planned JIT/AOT compilation that would further magnify the runtime advantages of knowing types at compile time. (docs.godotengine.org)
