You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* fix new 1.81.0 warning and clippy error
on 1.81, this expression caused rustc warning, and clippy error:
```
warning: this function depends on never type fallback being `()`
--> bin/propolis-cli/src/main.rs:497:1
|
497 | / async fn migrate_instance(
498 | | src_client: Client,
499 | | dst_client: Client,
500 | | src_addr: SocketAddr,
501 | | dst_uuid: Uuid,
502 | | disks: Vec<DiskRequest>,
503 | | ) -> anyhow::Result<()> {
| |_______________________^
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #123748 <rust-lang/rust#123748>
= help: specify the types explicitly
note: in edition 2024, the requirement `!: FromIterator<()>` will fail
--> bin/propolis-cli/src/main.rs:598:20
|
598 | .collect::<anyhow::Result<_>>()?;
| ^^^^^^^^^^^^^^^^^
= note: `#[warn(dependency_on_unit_never_type_fallback)]` on by default
warning: `propolis-cli` (bin "propolis-cli") generated 1 warning
```
i am, honestly, entirely missing how the never type is involved here, or how
changing the `collect`'s type from `anyhow::Result<_>` to `anyhow::Result<()>`
changes things in a direction to satisfy rustc. but bounding the type further
doesn't seem like it would cause a problem?
* the unused pub(crate) struct warnings are new also, allow these cases
0 commit comments