Search

Partial template specialization error with namespace & final by 顾益

Resolved
as Fixed Help for as Fixed

1
0
Sign in
to vote
Type: Bug
ID: 762838
Opened: 9/15/2012 2:12:21 AM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
My description is quite clear, please look at the code in VC++:
//header.h
#pragma once
namespace N
{
template <typename T>
class A final {};
template <typename T>//the partial specialization
class A<const T> final {};
}

//main.cpp
#include "header.h"
void main() {}

to the code above, the compiler will crash! reporting C1001 error.
please check, thank you.
Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling Version

Visual Studio 2012

Steps to reproduce

Please read the description, it's clear.

Product Language

Chinese - Simplified

Operating System

Windows 7

Operating System Language

Chinese (Simplified)

Actual results

The Visual C++ Compiler cl.exe can't work properly when template specialization, namespace and final keyword been used together.

Expected results

Please fix the bug, and please support C++11 better, I'm expect the next version of VC++ can totally support the C++11 standard.
thank you.
File Attachments
File Name Submitted By Submitted On File Size  
main.cpp 9/15/2012 40 bytes
vc bug.rar 9/15/2012 253 bytes
Sign in to post a comment.
Posted by Microsoft on 1/11/2013 at 12:32 PM
Hi,
Thanks for reporting the issue. It surely was crashing . We have fixed the issue on our end and the fix will be available in future releases of Visual Studio. We appreciate your feedback.Thanks

regards
Rashid Sarwar
Visual C++ team
Posted by 顾益 on 11/21/2012 at 5:37 PM
In the 2012 Nov. CTF, the bug still exist.
Posted by Microsoft on 9/16/2012 at 7:37 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 9/15/2012 at 2:52 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.