Remove use of unstable const_type_id feature (fixes CI failures on 1.47+) #418
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
const_type_id
feature was planned to stabilize in Rust 1.47, but this was reverted in rust-lang/rust#77083.build.rs
currently assumes the feature is stable in Rust 1.47 and later. This now causes errors when buildinglog
with thekv_unstable
feature on beta and nightly, which in turn is causing CI to fail on master.This patch simply removes the code that uses this feature, since it is not clear when it might be stabilized. Alternatively, the code could be kept around behind a second, nightly-only Cargo feature if it is still useful to someone. CC @KodrAus who added this code in #396.