-
-
Notifications
You must be signed in to change notification settings - Fork 21.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues in GDScript parser with assert() function and its arguments #39324
Comments
GDScript is being rewritten from the ground up: #39093 |
Yes, I know, it is being rewritten, I’ve read the news post on the site. And now I've skimmed through the code of new GDScript... And now I'm feeling much more worried than before, because… well, the old GDScript is at least somehow field tested by community (though, I’m puzzled that nobody ever encountered the bug I’ve described in this issue). The new code however is…totally new (that is not bad by itself). But I was unable to find any tests of it (we’re aren’t calling |
See https://github.com/godotengine/gdscript-tests. |
Can't rest right now but I think this assert evaluation bug might be fixed in 3.2.2 beta 4. |
That is very good to hear, thank you! |
this bug already fixed and cherrypicked : bd081df in 3.2.2 beta 3 it's working as expected |
Godot version: latest stable 3.2.1
OS/device including version: W7 x64, but it shouldn't matter probably
Issue description: put the following code in
cbasen.gd
Try the following code for derived class
I walked in gdscript parser under debugger while parsing code of the derived class. The parser indeed does know nothing about myfunc(), though it successfully parses
cbasen.gd
.This issue cost me about half a work day to pinpoint.
It is soooo discouraging... Even more so after looking at the source code that completely lacks any sanity checks and state assertions...
The text was updated successfully, but these errors were encountered: