Waffle Maybe

`cargo audit` can also output something like ``` 3 errors were suppressed because of whitelist. Use `cargo audit --ignore-whitelists` to see them. ```

I think that it's expected that timezone offset is either inferred from `language_code` or explicitly asked from the user (maybe even both).

It's weird that `owo-colors` has unsafe given this line from the [readme](https://github.com/jam1garner/owo-colors/blob/8c1d8324e0bedb3121958d98a5352bc2943b8aef/README.md): > No allocations, unsafe, or dependencies required because embedded systems deserve to be pretty too uwu. The only...

Seeing https://github.com/rust-lang/stdarch/runs/7917316301?check_suite_focus=true (doc only change) I think CI fails not because of my changes 🤔

Rebased 👍🏻

Every`clippy::restriction`, `clippy::pedantic`, `clippy::nursery` and `clippy::cargo` is allow by default, so there is no need to allow them explicitly. And `#![allow(clippy::all)]` will suppress _all_ clippy warnings, doesn't it?

A bit of an update: `future_closure` from the original issue now [works with `#![feature(impl_trait_in_fn_trait_return)]`](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=d1c0c3cbdf0a33f390c62c05f8d0459c) ([tracking issue](https://github.com/rust-lang/rust/issues/99697)): ```rust #![feature(impl_trait_in_fn_trait_return)] use core::future::Future; fn future_closure() -> impl Fn() -> impl Future { let...

It seems like the same thing happens to rustfmt: `x b rustfmt` doesn't include rustfmt as part of the built rust toolchain, meaning that `rustfmt +custom-toolchain` doesn't work.

@rustbot claim

I forget that clippy exists every time xd