fix clippy default warning

update rust-version: 1.60.0 ==> 1.63.0

general: apply clippy lints (#407)

* general: update crates to 2021 edition.

* general: apply clippy --fix

* general: apply manual clippy lints

* cargo fmt.

Remove trailing spaces in 'README.md' files

Silence `clippy::type_complexity` warning in tests

Replace if-let with `Ok(())` & `Err(err)` arms on result with `result.map(|_| ())`

Replace `Box::new(T::default())` with `Box::<T>::default()`

Replace `assert!(false, …)`/`assert!(false)` with `panic!(…)`/`panic!()`

Unify `assert_eq!(…)`/`assert_ne!(…)` to take args in order of `…!(actual, expected)`

While there isn't an explicit convention for this in Rust the stdlib docs all use `assert_eq!(actual, expected)`

Unify `assert_eq!(…)`/`assert_ne!(…)` to take args in order of `…!(actual, expected)`

While there isn't an explicit convention for this in Rust the stdlib docs all use `assert_eq!(actual, expected)`, making it a sort of implicit convention.

show more ...

upgrade to chrono 0.4.23

Fix clippy for rust 1.66 (#369)

Release mdns version 0.5.2

Adjust logging levels in mDNS (#366)

Before this module would `info` log and every packet
it received. It has been updated to match the `ice` module
and use the trace level for incoming packets.

Release mdns version 0.5.1

Release util version 0.7.0

Add MSRV policy and update MSRV to 1.60.0 (#337)

Add rust-version

Revert "Add rust-version to Cargo.toml"

This reverts commit 5a263440b18854c7ffd9b47ebea6260934da0ad9.

Turns out this was only added in Cargo version 1.64.0 so it breaks CI.

Add rust-version to Cargo.toml

Bump all sub crate versions (#286)

Update changelogs for subcrate releases (#285)

Introduce change logs for all crates (#279)

mdns: get_interface_addr_for_ip once per query (#275)

Specify both path and version in crate deps

Cargo allows specifying both a `path` and `version` for dependencies,
doing this makes publishing easier.

> It is possible to specify both a registry ver

Specify both path and version in crate deps

Cargo allows specifying both a `path` and `version` for dependencies,
doing this makes publishing easier.

> It is possible to specify both a registry version and a git or path
> location. The git or path dependency will be used locally (in which
> case the version is checked against the local copy), and when
> published to a registry like crates.io, it will use the registry
> version. Other combinations are not allowed.

_From [The Cargo Book][0]_

[0]: https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#multiple-locations

show more ...

Remove .github files from previous repos

These files are no longer relevant since the merge into a monorepo.