Skip to content

GDScriptFunctionState, Async implementation. #868

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.

Sign up for GitHub

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

Jump to bottom
Closed
darthLeviN opened this issue Aug 21, 2024 · 2 comments
Closed

GDScriptFunctionState, Async implementation. #868

darthLeviN opened this issue Aug 21, 2024 · 2 comments
Labels
feature Adds functionality to the library status: duplicate This issue or pull request already exists

Comments

@darthLeviN
Copy link

darthLeviN commented Aug 21, 2024 •
edited
Loading

My suggestion is to expose GDSCriptFunctionState and implement Future for it or it's wrappers.

I wanted to do this but i read that i should make an issue and discuss it first because it's big change.

Is this a useful thing to enable seamless await/async calls in the future?
@Bromeon Bromeon added the feature Adds functionality to the library label Aug 21, 2024
@TitanNano
Copy link
Contributor

GDSCriptFunctionState exposes a connected signal, so if #261 gets implemented, we can convert the function state into a signal future.

@Bromeon
Copy link
Member

Bromeon commented Aug 31, 2024

Please continue discussion under #261, there are ongoing ideas/efforts.

@Bromeon Bromeon closed this as not planned Won't fix, can't repro, duplicate, stale Aug 31, 2024
@Bromeon Bromeon added the status: duplicate This issue or pull request already exists label Aug 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature Adds functionality to the library status: duplicate This issue or pull request already exists
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Bromeon @TitanNano @darthLeviN