Skip to content
TheChatArchiveThe Chat Archive
gpt-5.6-luna· openaiHugging Face ibragim-bad/swe_rebench_07_2026_trajectories

ISSUE DESCRIPTION Cannot complete macro path in macro <!-- Troubleshooting guide:…

  1. User

    ISSUE DESCRIPTION

    Cannot complete macro path in macro

    rust-analyzer version: rust-analyzer 0.4.2897-standalone

    rustc version: rustc 1.97.0-nightly (36ba2c771 2026-04-23)

    editor or extension: Vim

    code snippet to reproduce:

    macro_rules! bar { () => (); }
    macro_rules! foo { ($i:ident) => { $i!() }; }
    fn main() {
        foo!(bar$0);
    }
    

    ADDITIONAL ADVICE

    Since you are given a git repository, you can use git commands to simplify your work. For example, if you made a mistake and want to revert your changes, you can use git checkout <file> to restore the file to its original state. You can also reset all changes in the repository using git reset --hard command. Additionally, you can use git stash and git stash pop to temporarily save your changes and restore them later. Finally, you can see the changes that you've made (which will be submitted when you call submit) using git status or git diff commands. However you don't need to use git add or git commit before submitting your changes. In fact, submit only submits currently unstaged changes because it uses git diff to get the changes that need to be submitted.

    CHECKLIST

    Before submitting your solution, please go over the following checklist and make sure you've done everything:

    • If an error was reported in the issue description, I have successfully reproduced it.
    • If an error was reported in the issue description, I have confirmed that my fix resolves the error.
    • I have thought about edge cases and made sure my fix handles them as well.
    • I have run existing tests in the repository that might have been affected by the change I made and confirmed that they pass. I want you to list every bullet from this checklist and write your reasoning for why you think you did it or didn't need to.

    Repository has been uploaded and your shell is currently at the repository root. Time to solve the issue!

    (Current directory: /rust-analyzer, current file: none) bash-$

  2. Assistant

    I’ll trace macro completion handling and the syntax/token classification used at the cursor, then reproduce with the relevant completion tests. I’ll make the smallest source change, run focused tests (and broader checks if practical), and inspect the final diff before submitting.

  3. Assistant

    rg is unavailable in this environment, so I’ll use grep/find instead and inspect the completion crate structure.

  4. Assistant

    The failure is in speculative macro expansion: completion inside foo! is mapped into the generated bar!() call, and the engine tries to expand bar even though the cursor is on that macro call’s path. The speculative token (bar plus the completion marker) cannot resolve as a macro, so expansion aborts before normal macro-name completion runs. I’ll make expansion stop at a macro-call path, while retaining expansion for cursors inside macro arguments.

  5. Assistant

    The change is localized and preserves the existing behavior for macro arguments: it only short-circuits when the speculative token lies within a macro call’s path. The repository has no installed Rust toolchain, so Cargo tests cannot run; I did run whitespace/diff validation and checked the API patterns against existing code. I’ll now review the final diff and submit.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.