This commit switches away from implicitly enabling the min_specialize Rust nightly feature whenever a Nightly compiler is used to instead requiring an explicit opt-in with a new Cargo feature nightly-specialize. The goal of this commit is to fix #238 and has two primary motivations:
In #238 I'm trying to build something that depends on this crate as part of the Rust bootstrap process but this crate fails to build due to min_specialize not being allowed but a nightly compiler is in use. This is due to the fact that the way -Zallow-features is managed in the bootstrap is different than the standard Cargo way of doing so.
This removes a failure mode where if one day the min_specialize feature changes this crate won't break when built on nightly. Users of Nightly compilers will be able to continue using this crate if the feature was not explicitly opted-in to.
This commit switches away from implicitly enabling the
min_specializeRust nightly feature whenever a Nightly compiler is used to instead requiring an explicit opt-in with a new Cargo featurenightly-specialize. The goal of this commit is to fix #238 and has two primary motivations:In #238 I'm trying to build something that depends on this crate as part of the Rust bootstrap process but this crate fails to build due to
min_specializenot being allowed but a nightly compiler is in use. This is due to the fact that the way-Zallow-featuresis managed in the bootstrap is different than the standard Cargo way of doing so.This removes a failure mode where if one day the
min_specializefeature changes this crate won't break when built on nightly. Users of Nightly compilers will be able to continue using this crate if the feature was not explicitly opted-in to.