feat(rust): access OptState in LazyFrame to unit-test optimization toggle methods.
#9883
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
github-actions
bot
added
enhancement
|
Yeap, seems fine. 👍 |
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.
rust-polars
LazyFrameis wrapped in e.g. py-polars r-polars nodejs-polars and many other rust projects.It is difficult to unit-test optimizations switches in
OptState, because there is no public getter-method.Setting such states has had a bug in the past.
With
get_current_optimizations()in rust-polars, it is straight forward to unit-test optimization choices.If PR is OK I can also add unit-tests for py-polars