


Is Microsoft Visual C 's Two-Phase Template Instantiation Truly Broken, and If So, How?
Dec 07, 2024 pm 12:13 PMMicrosoft Visual C 's Misunderstood "Broken" Two-Phase Template Instantiation
Introduction
Microsoft Visual C (MSVC) has often been criticized for its alleged flawed implementation of two-phase template instantiation. This article delves into the specifics of this criticism, examining the underlying issue and providing a detailed explanation.
The Two-Phase Template Instantiation Controversy
Two-phase template instantiation is a process in C where template classes and functions are first syntactically checked for correctness, and then complete instantiation occurs at later usage sites. However, claims have been made that MSVC does not properly implement this mechanism.
Early Understanding of the Issue
Initially, it was believed that MSVC only performed basic syntax checks on template definitions, ignoring whether names used in the template were declared. However, this understanding is incomplete.
The True Nature of the Issue
The actual issue with MSVC's two-phase template instantiation comprises two interconnected layers:
Layer 1: Incorrect First Phase Lookup
MSVC fails to perform early (first phase) lookup for non-dependent expressions, such as in the example:
int foo(void*); template<typename T> struct S { S() { int i = foo(0); } }; void foo(int);
MSVC postpones this lookup to the second phase, where it mistakenly binds the expression to 'foo(int)', resulting in an error.
Layer 2: Incorrect Second Phase Lookup
The second phase of template lookup in MSVC is also flawed. While the C standard specifies that ADL-nominated namespaces are extended in the second phase, MSVC erroneously extends non-ADL lookup as well.
This can be illustrated with the following example:
namespace N { struct S {}; } void bar(void *) {} template <typename T> void foo(T *t) { bar(t); } void bar(N::S *s) {}
Despite being dependent, the call to bar(t) is incorrectly resolved to void bar(N::S *s), demonstrating the improper behavior of MSVC's second phase lookup.
Conclusion
Microsoft Visual C 's implementation of two-phase template instantiation is indeed flawed, but not in the simplistic manner originally understood. The issue is a complex interplay between incorrect first and second phase lookups that can result in errors or incorrect behavior for certain code constructions.
The above is the detailed content of Is Microsoft Visual C 's Two-Phase Template Instantiation Truly Broken, and If So, How?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

Yes, function overloading is a polymorphic form in C, specifically compile-time polymorphism. 1. Function overload allows multiple functions with the same name but different parameter lists. 2. The compiler decides which function to call at compile time based on the provided parameters. 3. Unlike runtime polymorphism, function overloading has no extra overhead at runtime, and is simple to implement but less flexible.

C has two main polymorphic types: compile-time polymorphism and run-time polymorphism. 1. Compilation-time polymorphism is implemented through function overloading and templates, providing high efficiency but may lead to code bloating. 2. Runtime polymorphism is implemented through virtual functions and inheritance, providing flexibility but performance overhead.

Yes, polymorphisms in C are very useful. 1) It provides flexibility to allow easy addition of new types; 2) promotes code reuse and reduces duplication; 3) simplifies maintenance, making the code easier to expand and adapt to changes. Despite performance and memory management challenges, its advantages are particularly significant in complex systems.

Implementing polymorphism in C can be achieved through the following steps: 1) use inheritance and virtual functions, 2) define a base class containing virtual functions, 3) rewrite these virtual functions by derived classes, and 4) call these functions using base class pointers or references. Polymorphism allows different types of objects to be treated as objects of the same basis type, thereby improving code flexibility and maintainability.

C destructorscanleadtoseveralcommonerrors.Toavoidthem:1)Preventdoubledeletionbysettingpointerstonullptrorusingsmartpointers.2)Handleexceptionsindestructorsbycatchingandloggingthem.3)Usevirtualdestructorsinbaseclassesforproperpolymorphicdestruction.4

Polymorphisms in C are divided into runtime polymorphisms and compile-time polymorphisms. 1. Runtime polymorphism is implemented through virtual functions, allowing the correct method to be called dynamically at runtime. 2. Compilation-time polymorphism is implemented through function overloading and templates, providing higher performance and flexibility.

C polymorphismincludescompile-time,runtime,andtemplatepolymorphism.1)Compile-timepolymorphismusesfunctionandoperatoroverloadingforefficiency.2)Runtimepolymorphismemploysvirtualfunctionsforflexibility.3)Templatepolymorphismenablesgenericprogrammingfo

People who study Python transfer to C The most direct confusion is: Why can't you write like Python? Because C, although the syntax is more complex, provides underlying control capabilities and performance advantages. 1. In terms of syntax structure, C uses curly braces {} instead of indentation to organize code blocks, and variable types must be explicitly declared; 2. In terms of type system and memory management, C does not have an automatic garbage collection mechanism, and needs to manually manage memory and pay attention to releasing resources. RAII technology can assist resource management; 3. In functions and class definitions, C needs to explicitly access modifiers, constructors and destructors, and supports advanced functions such as operator overloading; 4. In terms of standard libraries, STL provides powerful containers and algorithms, but needs to adapt to generic programming ideas; 5
