Introduce experimental feature warning #2622
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
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.
Issue
Description
Every now and then, we introduce experimental features in Flower. So far, there is no consistent way to inform the user about the experimental nature of a feature.
Related issues/PRs
Once this PR is merged, PR #2393 can be updated to use
warn_experimental_featureProposal
Explanation
This PR introduces a utility function
warn_experimental_featurethat we can use to log a warning every time a user uses an experimental feature. In addition to that, once we use the utility throughout the codebase, it will also allow us to easily search for experimental features.Checklist
#contributions)