-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Deprecate ScalarUDF::invoke and invoke_no_args for invoke_batch #13179
Deprecate ScalarUDF::invoke and invoke_no_args for invoke_batch #13179
Conversation
`invoke_batch` is the one used now. The others are no longer in use and we should deprecate and remove them.
@@ -96,6 +96,7 @@ fn criterion_benchmark(c: &mut Criterion) { | |||
|
|||
b.iter(|| { | |||
black_box( | |||
#[allow(deprecated)] // TODO use invoke_batch |
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.
can we do #[warn(deprecated)]
instead? My vision it should output the note
in this case?
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 though we treat warnings as errors. will this work?
Like that
This will make the code cleaner |
@comphead thanks for your suggestion. i tried this. I changed one of the suppressions to
it looks like these lines are crucial
|
oh bummer -D denies warning, let me check real quick if we can introduce any exclusions |
@comphead thanks |
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.
lgtm thanks @findepi
Lets go with PR and later I can play with exclusions |
invoke_batch
is the one used now. The others are no longer in use and we should deprecate and remove them.Extracted from #13174