rust-lang / rust-lang/rust

Tracking Issue for `global_asm!` in statement positions

Open
#156,965 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

B-experimental C-tracking-issue T-lang
Dominant language
Rust
Stars
119k
Forks
16.1k
PR merge metrics
PR metrics pending

Description

The feature gate for the issue is #![feature(global_asm_statement_position)].

About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Discussion comments will get marked as off-topic or deleted.
Repeated discussions on the tracking issue may lead to the tracking issue getting locked.

Description

Currently global_asm! is only allowed in a module root. This feature allows it to appear in any position an item can appear.

mod foo {
    // This was previously the only allowed position.
    global_asm!("");

    fn bar() {
        // Like any item, `Baz` can be added inside a function,
        // but has no relation to the parent function `bar()`.
        struct Baz;

        // This is not allowed today, its what this feature enables.
        global_asm!("");
    }
}
Steps
Implementation history
  • #156582
  • #156855
  • #156884
  • #156919

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the feature gate global_asm_statement_position and the implementation history, especially #156919. Review the linked Rust Reference PR #2272 and the stabilization guide to understand the remaining documentation and stabilization work. Done means the implementation, documentation, and stabilization checklist items are addressed.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
compilers
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.