F43 Change Proposal: Deprecate async-std (self-contained)

Project Discussion Change Proposals
,
1

:link: Deprecate the async-std Rust crate

This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.

Wiki
Announced

:link: Summary

The async-std Rust crate is no longer maintained and was deprecated in favor of the smol crate by the upstream project. This Change is about marking the package for this Rust crate as deprecated() too to reflect this.

:link: Owner

:link: Detailed Description

The async-std crate has officially been discontinued with the release of version 1.13.1. The recommended replacement is the smol crate, which builds on some of the same building blocks as async-std, but which is stil actively maintained. Alternatively, the tokio crate provides a much more widely used async runtime.

:link: Feedback

N/Y

:link: Benefit to Fedora

No new packages that are added to Fedora will depend on a library that was officially discontinued.

Eventually, as existing packages migrate to other async runtimes, it should be possible to remove packages for the async-std crate from Fedora repositories entirely.

:link: Scope

  • Proposal owners:

Add Provides: deprecated() to the rust-async-std-devel package.

  • Other developers:

N/A

  • Release engineering:

N/A

  • Policies and guidelines:

N/A

  • Trademark approval:

N/A

  • Alignment with the Fedora Strategy:

N/A

:link: Upgrade/compatibility impact

N/A

:link: Early Testing (Optional)

N/A

:link: How To Test

A DNF repoquery --provides rust-async-std-devel should include deprecated().

:link: User Experience

N/A

:link: Dependencies

N/A

:link: Contingency Plan

  • Contingency mechanism: N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change)

:link: Documentation

:link: Release Notes

N/A

Last edited by @amoloney 2025-05-06T11:19:21Z

Last edited by @amoloney 2025-05-06T11:19:21Z

2

How do you feel about the proposal as written?

  • Strongly in favor
  • In favor, with reservations
  • Neutral
  • Opposed, but could be convinced
  • Strongly opposed
0 voters

If you are in favor but have reservations, or are opposed but something could change your mind, please explain in a reply.

We want everyone to be heard, but many posts repeating the same thing actually makes that harder. If you have something new to say, please say it. If, instead, you find someone has already covered what you’d like to express, please simply give that post a :heart: instead of reiterating. You can even do this by email, by replying with the heart emoji or just “+1”. This will make long topics easier to follow.

Please note that this is an advisory “straw poll” meant to gauge sentiment. It isn’t a vote or a scientific survey. See About the Change Proposals category for more about the Change Process and moderation policy.