-
-
Notifications
You must be signed in to change notification settings - Fork 477
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
Fix variant call compiler error #1017
Conversation
Any chance for this to be reviewed soon? As it is currently a blocking point regarding one of our projects... BTW I do know that everyone is busy with 1.0 stable coming soon. |
This is currently a huge blocking point for me as well. Any chance of this getting reviewed soon? |
@akien-mga may I tag you here. This is critical for some plugin development. |
Any update on this? This issue is still blocking for me, (well at this point I have started using a fork with this PR applied). But I would like to not have to do that if possible. |
Unfortunately, I don't think anyone from the GDExtension team has had a chance to look at this yet. At the moment, we're really focused on finishing some things up before the 4.1 feature freeze in two week, but after that, we're going to switch to focusing on bug fixes. I've added this PR to my personal list of bugs to dig into! |
Sorry for taking so long to come back to this! I think your assessment that the compiler is getting confused between the two versions of I'm a little worried about this PR needing to add the |
I just created PR #1238 which starts from the changes here, rebases, makes the requested changes from review, and adds a unit test |
Superseded by #1238 |
Fixes #1015, the compiler gets confused because the function wasn't using
Variant **
. I tried to keep it as true to the original by usingstd::array
but I had to rename functions likecall
->callp
.