Create a custom future to prevent double boxing  #820

New issue

Copy link

New issue

Copy link

Open

#1256

Open

Create a custom future to prevent double boxing #820

#1256

Copy link

Labels

enhancementImprovement of existing features or bugfixImprovement of existing features or bugfixhelp wantedk::performanceRelated to performanceRelated to performance

Description

LegNeato

opened on Dec 10, 2020

Member

Issue body actions

We should fix this TODO:

juniper/juniper/src/types/async_await.rs

Line 264 in 2c15ea7

// TODO: implement custom future type instead of

Activity

LegNeato

added

enhancementImprovement of existing features or bugfixImprovement of existing features or bugfix

help wanted

k::performanceRelated to performanceRelated to performance

on Dec 10, 2020

jawang94

linked a pull request that will close this issue on May 4, 2024

• Refactor code to remove async move closure which may result in double… #1256

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

Metadata

Metadata

Assignees

No one assigned

Labels

enhancementImprovement of existing features or bugfixImprovement of existing features or bugfixhelp wantedk::performanceRelated to performanceRelated to performance

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

Code with agent mode

Select code repository

• Refactor code to remove async move closure which may result in double…graphql-rust/juniper

Participants

Issue actions