microsoft / microsoft/ifc-spec

Missing home scope on local variable

Open
#149 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TeX
Stars
94
Forks
11
Avg merge
1d 29m
Merged PRs (30d)
2

Description

consteval void foo() {}
consteval bool bar() {
    decltype(auto) f = &foo;
    return true;
}

The above variable is lacking home scope information and is thus written to the IFC file as if the original source was:

consteval void foo() {}
decltype(auto) f = &foo;
consteval bool bar() {
    return true;
}

I would expect the home scope to reference the function bar in this case.

Is this intentional/is there a rational for this representation or are we looking at a bug here?

Contributor guide

No contributing guide indexed for this repository

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 C++ example in the issue and inspect how the local variable and its enclosing function are represented in the IFC file. Compare the home-scope rules for local variables with the reported output; done when the specification explains whether bar must be referenced or confirms the current representation.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.