-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hello, - From time to time I see upstreams using -Werror (or, #[deny(warnings)] in Rust) which is definitely causing problems when gcc or any other compiler adds new warnings. Unfortunately, some upstreams reject removing -Werror and use it just for specific warnings. I'm thinking about passing --cap-lints warnings to rustc to prevent erroring on this (and just show warning). Should we do same for C/C++? Or should I reconsider decision in Rust land? - -- - -Igor Gnatenko -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEhLFO09aHZVqO+CM6aVcUvRu8X0wFAlp+pdsACgkQaVcUvRu8 X0yycg/9HqrMtz/e4mP7gDeyiWx5JNWDtnWj778RsLw5dB1LmO7FIgtZ724cIR6t GeLHbo+3Ap1nZpVJL+mlLJf9nAdVLQWRUn/pIUQFVDAlIuaSxnTT0LIE0qLCiLMb Zch9M55rNSSJQR1IvmWEuOB/X3/fYt3jTaovdzr1aaUKlY68yXPUWvdRXEOp3OPt 73SFZ1kzTwnSJ2XfFccEmoFV47A/YWqojzV5EwdvWWYtaHpfKjTjQOgWvoqCTbqW 7QTOZ700kaje0Kbh3lcksQvFo3E9siSng8UvO/RDlUoWs/vmC/f2u2+mN7FKU4Es Bgzt67UpnV7PeBqtaUKwRyvoC0AUNqxzVDtq3BFoNT8QOeCaxAjDi7/MWfxBxdmm 4UrEdwG7xXL/862UoEBUIXSWpAa40TKosjPkeJV3Bjnq44U/kp79xGpRzJgDgLIQ LITGCecfWvveQaP9TJPLBlkgkA/Bmmd0pmSioATfwOfKwJEND99x7QsE2urpA7Lp EsZf4p47LvJH5AvnDiMxojqfrKgND5bvHGtRCGVyBp0SlzkAfVmHM/MgLUrN03qx 0phKWyjuQqPsX1Nu2hL+zKHwkPD6ggfvIAuTZcwNeuZjkkglJMsP5Vx7oQl+Dtts PsCNAHdS87+piOpTPEd84isv9nMI5oti4sfHuSuf1NlG4Tvezqk= =smzF -----END PGP SIGNATURE----- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
