> This post unpacks how this happened — and why none of the individual components are technically "broken": 1. A 12-year-old overload resolution bug in G++ I

> This post unpacks how this happened — and why none of the individual components are technically "broken": 1. A 12-year-old overload resolution bug in G++ I don't know what author meant here. The whole issue exists because G++ overload resolution mechanism was broken.