-
Notifications
You must be signed in to change notification settings - Fork 1.5k
chore: fix clippy::large_enum_variant for DataFusionError #15861
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
comphead
merged 1 commit into
apache:main
from
rroelke:rroelke/gh-15860-clippy-large-enum-variant
Apr 29, 2025
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wondering why now the error needs to be boxed? 🤔
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't have the specific numbers but here's a verbose explanation of what the lint is trying to tell us about:
We can see here that the size of
MyErrorType
is 4096 (ish)Consequently the size of
Result<T, MyErrorType>
is always at least 4096.Result<usize, MyErrorType>
has size 4096. To calltry_thing
we have to allocate memory to hold that size of result. We don't return theusize
in a register. And most of the time we expect to seeOk
rather thanErr
so this makes the common case a lot worse.Boxing the large variants fixes the issue since it reduces the size of the variant to a pointer, which fits in a register.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we box other error type too?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd favor that. There might be another error variant which is less than the clippy threshold size but is still large enough to prevent certain optimizations. If all the error variants were boxed then we could be confident that DataFusionError could be copied around in registers and then perhaps
Result<T, DataFusionError>
also could be for smallT
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I personally suggest avoiding additional API churn (aka boxing all varaints) unless there is some particular problem we are trying to solve or improve performance in some way we can measure