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

Consider async for callbacks #33

Open

rtsuk opened this issue Mar 17, 2023 · 3 comments

Collaborator

rtsuk commented Mar 17, 2023

Collaborator Author

rtsuk commented Mar 17, 2023

Also https://crates.io/crates/executor

Member

boozook commented Aug 6, 2023

Is it really necessary? Yes, it's beautiful, but the huge amount of closures in futures will dramatically increase the stack. Isn't it?

Collaborator Author

rtsuk commented Aug 6, 2023

It's not necessary, but the callback-heavy nature of the Playdate API might make it the easiest course.

I think async closures tend to be allocated on the heap, since they outlive any single stack frame.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment