Fix Clippy warnings

[Weiteng Chen (CvvT)]

No description provided.

[Jay Bosamiya (Microsoft) (jaybosamiya-ms)]

The changes overall seem mostly reasonable, but I think the RUSTFLAGS changes for the CI are problematic for downstream customers. We need to fix the underlying issue itself.

If it helps unblock things, a "cheaper" solution is to put an allow(deprecated) for the atomic fetch_update

[Jay Bosamiya (Microsoft) (jaybosamiya-ms)]

Something like 4629f4c from #1469 would act to unblock things

[Weiteng Chen (CvvT)]

The changes overall seem mostly reasonable, but I think the RUSTFLAGS changes for the CI are problematic for downstream customers. We need to fix the underlying issue itself.

If it helps unblock things, a "cheaper" solution is to put an allow(deprecated) for the atomic fetch_update

I didn't use allow because in ulitebox there are ~15 functions using fetch_update. Let's see if we can bump the nightly version. If not, I agree it is better to use allow for now.

[github-actions]

🤖 SemverChecks 🤖 No breaking API changes detected

Note: this does not mean API is unchanged, or even that there are no breaking changes; simply, none of the detections triggered.

[Jay Bosamiya (Microsoft) (jaybosamiya-ms)]

Thanks Weiteng!