Rust-GCC / Rust-GCC/gccrs

gccrs incorrectly parses a fake turbofish operator

Open
#3,388 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
2.9k
Forks
231
Avg merge
19h 55m
Merged PRs (30d)
67

Description

Summary

not<true>(); should actually be written as not::<true>();, i.e. a turbofish operator. It seems though that this survives the parsing phase.

Reproducer

I tried this code:

fn not<const A: bool>() {
    let _ = if A
        { "A" }
    else
        { "B" }
    ;
}

fn main() {
    not<true>();
}
Does the code make use of any (1.49) nightly feature ?
  • Nightly
Godbolt link

No response

Actual behavior
TRS-E14 cgen $ gccrs main.rs
main.rs:2:16: error: Cannot find path ‘A’ in this scope [E0433]
    2 |     let _ = if A
      |                ^
Expected behavior
TRS-E14 cgen :( $ rustc main.rs
error: comparison operators cannot be chained
  --> main.rs:10:8
   |
10 |     not<true>();
   |        ^    ^
   |
GCC Version

b87fd67fa807665d741968b7aca4b9399f2071db

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 by running the supplied Rust reproducer with gccrs and rustc and compare where parsing diverges. Trace the parser path for not<true>(); done means gccrs rejects the fake turbofish as a chained comparison instead of continuing into the function body and reporting A as an unresolved path.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, rust
Domain
compilers
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.