On Friday, 4 April 2025 13:07:12 Pacific Daylight Time Milian Wolff wrote: > Agreed to all of this. But for me at least, the impact of visibility on non- > polymorphic types, which you don't use dynamic cast nor throw as > exceptions, was, so far, not clear at all. And this is the "new" part. Also > note again the clear rule that I also learned from Marc that one should not > wholesale export all-inline types, which goes against this 🙁
We can also argue this issue is QoI for std::any for the implementations at hand. The Standard requires an API to get the typeinfo, but it does not require *using* it as the discriminator. Implementations that support shared libraries and DLLs should be fixed to compare type names like QMetaType does. I mean, we do have 20 years of experience with this, since Qt 4.0. -- Thiago Macieira - thiago.macieira (AT) intel.com Principal Engineer - Intel DCAI Platform & System Engineering
smime.p7s
Description: S/MIME cryptographic signature
-- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
