microsoft / microsoft/STL

`<typeinfo>`: non-Standard extension `type_info::raw_name`

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

Nobody has claimed this yet.

bug vNext
Dominant language
C++
Stars
11.1k
Forks
1.7k
Avg merge
4d 15h
Merged PRs (30d)
22

Description

Describe the bug
The method type_info::raw_name exists, it works and no warning that it is non-Standard is emitted

Command-line test case

#include <iostream>
#include <typeinfo>

using namespace std;

int main()
{
    cout << typeid(cout).raw_name();
}
D:\temp2>cl /W4 /EHsc test.cpp
Microsoft (R) C/C++ Optimizing Compiler Version 19.30.30423 for x64
Copyright (C) Microsoft Corporation.  All rights reserved.

test.cpp
Microsoft (R) Incremental Linker Version 14.30.30423.0
Copyright (C) Microsoft Corporation.  All rights reserved.

/out:test.exe
test.obj

D:\temp2>test
.?AV?$basic_ostream@DU?$char_traits@D@std@@@std@@

Expected behavior
Non Standard method called like _Raw_name() or does not exist

STL version

Microsoft Visual Studio Professional 2022 Preview (64-bit)
Version 17.0.0 Preview 3.1

Additional context

vNext note: Resolving this issue will require breaking binary compatibility. We won't be able to accept pull requests for this issue until the vNext branch is available. See #169 for more information.

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 implementation and the type_info::raw_name entry point, then run the provided C++ command-line test case. The issue is complete when this non-Standard API is renamed to _Raw_name() or removed, with the expected compatibility impact handled on the vNext branch.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.