Skip to content

Tracking issue for #!feature(async_unsafe)] (RFC 2394) #62501

Description

@Centril

This is a tracking issue for #![feature(async_unsafe)] (rust-lang/rfcs#2394).
The feature gate provides the async unsafe fn syntax.

Steps:

Unresolved questions:

  • Is this the right design wrt. calling async unsafe fn?

Activity

  1. added
    A-frontendArea: Compiler frontend (errors, parsing and HIR)
    T-langRelevant to the language team
    B-unstableBlocker: Implemented in the nightly compiler and unstable.
    B-RFC-implementedBlocker: Approved by a merged RFC and implemented but not stabilized.
    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFC
    AsyncAwait-TriagedAsync-await issues that have been triaged during a working group meeting.
    on Jul 8, 2019
  2. Centril commented on Jul 11, 2019

    @Centril
    ContributorAuthor

    I was convinced not to feature gate this after all (see #62149 (comment)). Sorry about the noise!

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

    A-async-awaitArea: Async & AwaitA-frontendArea: Compiler frontend (errors, parsing and HIR)AsyncAwait-TriagedAsync-await issues that have been triaged during a working group meeting.B-RFC-implementedBlocker: Approved by a merged RFC and implemented but not stabilized.B-unstableBlocker: Implemented in the nightly compiler and unstable.C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCT-langRelevant to the language team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions