Remove associated_consts feature #11
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Could you release 0.2.1 with these changes? :) |
|
Sure thing! I'll release it later today once the 1.20 compiler gets officially released. |
|
Ping |
|
The version on crates.io is 0.2.1 now, I just haven't committed it to github. EDIT: Done. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Associated consts is stabilized in the current form used by drm-rs, already works in beta and will be in rust stable 1.20. (see rust-lang/rust#29646 (comment))
Using the feature flag prevents compilation on beta, as the feature flag is generally not allowed on stable and beta channels even if the feature in question is already stabilized.
tl;dr This fixes compilation on current beta and upcoming stable 1.20