Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Make implicitly dependent feature explicitly depend on each other (#1551
) * Make implicitly dependent feature explicitly depend on each other By running a variant of cargo hack, we found a number of compile issues when using unusual feature combinations, and these are largely rectified by making intended feature pairings explicit. Client features now depend on the `client` feature, runtime features now depend on the `runtime` feature, etc. - rustls-tls / openssl-tls => `client` feature - oauth / oidc / gzip / socks5 / http-proxy => `client` feature - unstable-runtime => `runtime` feature Unfortunately, the cargo hack solution is simplistic and cannot verify everything AFAIKT yet. I am currently running with excluding oauth and oidc because these require picking a tls stack and we have an intended compile error for this. I cannot find a way to tell `hack` to model this without just excluding them. The number of features makes the combination features test very long, case in point, the cargo hack invocation in the justfile: - tests **11370** feature combinations - takes >2h (currently 30m in at 2000 combination on a beefy 7950X3D) Signed-off-by: clux <[email protected]> * update and run in ci Signed-off-by: clux <[email protected]> * opt in to hack ci Signed-off-by: clux <[email protected]> * also group derive with other core feature Signed-off-by: clux <[email protected]> --------- Signed-off-by: clux <[email protected]>
- Loading branch information