Skip to content
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

Create a custom future to prevent double boxing #820

Open
LegNeato opened this issue Dec 10, 2020 · 0 comments · May be fixed by #1256
Open

Create a custom future to prevent double boxing #820

LegNeato opened this issue Dec 10, 2020 · 0 comments · May be fixed by #1256
Labels
enhancement Improvement of existing features or bugfix help wanted k::performance Related to performance

Comments

@LegNeato
Copy link
Member

We should fix this TODO:

juniper/juniper/src/types/async_await.rs

Line 264 in 2c15ea7

// TODO: implement custom future type instead of

@LegNeato LegNeato added enhancement Improvement of existing features or bugfix help wanted k::performance Related to performance labels Dec 10, 2020
@jawang94 jawang94 linked a pull request May 4, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement Improvement of existing features or bugfix help wanted k::performance Related to performance
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Refactor code to remove async move closure which may result in double… jawang94/juniper
1 participant
@LegNeato