rwf2/Rocket

Phase out async_trait macro

Open

#2,684 opened on Dec 30, 2023

View on GitHub
 (5 comments) (6 reactions) (0 assignees)Rust (1,645 forks)batch import
acceptedhelp wantedrequest

Repository metrics

Stars
 (25,738 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

What's missing?

Rocket currently re-exports the async_trait crate for use with its Fairing (and possibly others). As of rust 1.75.0 this is no longer needed, therefore it would be nice to get rid of this dependency and use actual async functions for these traits.

This generally improves compile times, dependency count and IDE responsiveness.

Ideal Solution

For v0.6, remove async_trait (or put its usage behind a feature) and use async functions directly. This would raise the MSRV to 1.75.0.

Why can't this be implemented outside of Rocket?

This is an integral part of Rocket.

Are there workarounds usable today?

No. You bypass the need for the macro attribute by returning a Box<dyn Future<Output = T> + Send + 'a>, but this is unwieldy.

Alternative Solutions

No response

Additional Context

No response

System Checks

  • I do not believe that this feature can or should be implemented outside of Rocket.
  • I was unable to find a previous request for this feature.

Contributor guide

Research direction
Identify all trait definitions in Rocket that use `#[async trait]` and replace them with `async fn` in trait definitions. Update the minimum supported Rust version (MSRV) to 1.75.0. Ensure fairings and other trait implementations compile without the macro.
Tech stack
rust
Domain
backendapi
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Rust
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60