Migrate GDScript to the GDExtension mechanism and overhaul the implementation
> [!WARNING] > * This proposal is **not** an official plan, but merely the author's personal vision. > * The concept described in this proposal entails major changes, some of which are breaking. Therefore, these changes are primarily targeted for Godot 5.0. > [!NOTE] > * "GDScript 3.0" is the unofficial name for the hypothetical next implementation of GDScript, by analogy with the unofficial term "GDScript 2.0". > * This proposal raises a complex and broad topic. The author aims to be specific within the limits of a high-level description. > * This proposal is based on this [document](https://gist.github.com/dalexeev/80ba4c4abda0637701a48095fb1604de), with some revisions and removal of redundant details. > * See also the following proposals. They are somewhat related, but this one suggests more extensive changes. > * #3369 > * #7950 ## Problem or limitation ### Motivation <details> <summary>Contents</summary> * GDScript was initially created as a very simple language, but over time its complexity and number of features increased. Users now expect GDScript to include many features common in general-purpose languages, such as interfaces/traits, nullable and union types, generic types, namespaces, and more. * The current GDScript implementation has significant code duplication and technical debt. It is becoming increasingly difficult to maintain, implement new major features (especially those related to the type system), and fix complex bugs (especially those related to
Posted by dalexeev on Apr 13, 2026, 5:29 AM
Tags
Related issues
- This is the biggest problem with contracts, there's simply no way to actually say "please always execute this check".
- I don't disagree with you on this, I worked my whole life in corporate and haven't worked as a OSS maintainer before, though I will _and ...
- the new VSCode UI, looks cute, i don't like it.
- I've been working on my own private harness for the past 8 months, and I've been collecting ideas from such repos I've stumbled upon.
- The way AI is able to interact with outside resources is pretty impressive, but the quality of code it produces to me is still questionab...
- Add PR-style review comments in Git Diff UI that feed into the active agent thread
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
ux (Software)
This is the biggest problem with contracts, there's simply no way to actually say "please always execute this check".
I don't disagree with you on this, I worked my whole life in corporate and haven't worked as a OSS maintainer before, though I will _and ...
the new VSCode UI, looks cute, i don't like it.
I've been working on my own private harness for the past 8 months, and I've been collecting ideas from such repos I've stumbled upon.
The way AI is able to interact with outside resources is pretty impressive, but the quality of code it produces to me is still questionab...
Add PR-style review comments in Git Diff UI that feed into the active agent thread
Thanks for indulging me so far, by the way, I really appreciate this discussion, it's very stimulating.
Migrate GDScript to the GDExtension mechanism and overhaul the implementation
Migrate GDScript to the GDExtension mechanism and overhaul the implementation
> [!WARNING] > * This proposal is **not** an official plan, but merely the author's personal vision. > * The concept described in this proposal entails major changes, some of which are breaking. Therefore, these changes are primarily targeted for Godot 5.0. > [!NOTE] > * "GDScript 3.0" is the unofficial name for the hypothetical next implementation of GDScript, by analogy with the unofficial term "GDScript 2.0". > * This proposal raises a complex and broad topic. The author aims to be specific within the limits of a high-level description. > * This proposal is based on this [document](https://gist.github.com/dalexeev/80ba4c4abda0637701a48095fb1604de), with some revisions and removal of redundant details. > * See also the following proposals. They are somewhat related, but this one suggests more extensive changes. > * #3369 > * #7950 ## Problem or limitation ### Motivation <details> <summary>Contents</summary> * GDScript was initially created as a very simple language, but over time its complexity and number of features increased. Users now expect GDScript to include many features common in general-purpose languages, such as interfaces/traits, nullable and union types, generic types, namespaces, and more. * The current GDScript implementation has significant code duplication and technical debt. It is becoming increasingly difficult to maintain, implement new major features (especially those related to the type system), and fix complex bugs (especially those related to
Comments (0)
No comments yet. Start the discussion.