On Wed, 2024-07-24 at 22:13 +0200, Albert Larsan wrote: > Know that this is one of the cases that is explicitly not covered > under > the stability guarantee, i.e that code without warnings may get > warnings > on the next version Agreed. > This, the crate should fix the bug, and a one-line patch is enough to > hide the issue downstream in Fedora, by adding an `#![allow(...)]` > line > at the start of the affected crate. I'd recommend putting this just over the one field causing the issue rather than the #! on the entire crate. > However, it would be better if the issue was really fixed by either > removing or using the unused field. Agreed. -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
