Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Take advantage of weak features in Rust 1.60 for TLS enablement #454

Merged
merged 1 commit into from Oct 21, 2022

Commits on Oct 21, 2022

  1. Take advantage of weak features in Rust 1.60 for TLS enablement

    Previously it was impossible to have a unified feature named `rustls` or
    `native-tls` that would turn on the respective TLS backend in the chosen
    transport (`reqwest` or `ureq`) as a feature of `<crate>/tls` would
    implicitly turn on `<crate>`.  Since Rust 1.60 it is now possible to
    specify this crate-feature enablement through the use of the question
    mark in `<crate>?/tls`, which will only enable the `tls` feature if
    `<crate>` was enabled through other means (another feature).
    
    Secondly we can now also let optional crates have the same name as a
    feature, and use `dep:<crate>` to refer to the crate instead of the
    dependency, making for a more pleasant experience without renames to
    underscore suffixes (that subsequently have to be dealt with in Rust
    code, e.g. with `use log_ as log;` renames).
    MarijnS95 committed Oct 21, 2022
    Copy the full SHA
    7b1f3cd View commit details
    Browse the repository at this point in the history