I added the compiler warnings by merging what I use in libepoxy,
graphene, json-glib, and what's in the existing autotools build. That
was done mostly to get the ball rolling, not as a commentary on
whether strict aliasing rules are good or bad.
In general, I'd expect us to review the compiler
Just wondering what the position on this is. I've seen a few conflicting
indications:
(1) The new meson patches pass -fno-strict-aliasing to GCC and Clang:
https://git.gnome.org/browse/gtk+/commit/?h=wip/meson=1e3daf3178bb3db56ab12a55195969857f685101
The rationale is "We don't want to build buggy
