-
-
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
Shaders: Allow trailing commas in function calls #86991
base: master
Are you sure you want to change the base?
Conversation
fc8dd82
to
ccc3b34
Compare
ccc3b34
to
0bf26c8
Compare
0bf26c8
to
2b341f5
Compare
Haven't tested but doesn't look like this fixes:
Or
If we allow it explicitly in function calls these should also be allowed IMO, or it makes things more inconsistent Further gdshaders don't allow trailing commas even in array definition, unsure if this matches glsl or not Edit: seems glsl allows trailing comma in arrays, will look at a fix for that here as it's a parity matter |
No, it doesn't. Those are parsed by an entirely different part of code.
Sure, I can do that. I'm just waiting for an actual decision on godotengine/godot-proposals#8840 before doing more work that might just end up being thrown away if someone decides trailing commas should not be allowed. |
Co-authored-by: A Thousand Ships <[email protected]>
This PR implements godotengine/godot-proposals#8840: allowing trailing commas in shader call function call argument lists like