Il 17/07/20 11:05, Lars Knoll ha scritto:
No, we should just static_assert for [[no_unique_address]] being available on 
the platforms where we expect it. That is, anywhere but on certain MSVCs.
Some older embedded toolchains don’t have the flag neither.
If we make it a configure feature, we open the door to BIC problems as we might 
accidentally turn it off in some builds.

We should simply add a static assert that the Qt and the applications build 
mode are compatible.

But what would be the advantage of switching from the union to the attribute? Saving 1 byte per class?

Thanks,
--
Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer
KDAB (France) S.A.S., a KDAB Group company
Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com
KDAB - The Qt, C++ and OpenGL Experts

Attachment: smime.p7s
Description: Firma crittografica S/MIME

_______________________________________________
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Reply via email to