Try not disabling designated initializer overides.

Sometimes initializing the same field twice indicates a bug, so see
whether we can leave it enabled and suppress the warning in cases where
it's probably not a bug (too bad GCC didn't let you specify a default
initializer with, for example:

	int foo[16] = {
		[] = 17,
		[12] = 34
	};

which would mean we wouldn't have to suppress that warning in
ui/text_import.c).

Note also that not all compilers that can produce this warning call the
option "-Woverride-init".

CMakeLists.txt

@@ -677,15 +677,6 @@ else() # ! MSVC
 		# -Wimplicit-function-declaration into an error by default.
 		#
 		-Werror=implicit
-		#
-		# the value used for uninitialized fields is 0 and cannot be changed
-		# the workaround is to initialize everything to the wanted default
-		# any subsequent initializers then cause this warning
-		#
-		# XXX: in theory c++20+ could have this issue aswell, but we don't
-		# use designated initializers in c++ code anyway.
-		#
-		-Wno-override-init
 	)
 
 	#