R-JunmingChen commented on PR #36739: URL: https://github.com/apache/arrow/pull/36739#issuecomment-1678311281
>I think it is possible to define 2 explicit public functions of the class SetLookupOptions: > >SetLookupOptions(Datum value_set, bool skip_nulls = false) (same as currently) >SetLookupOptions(Datum value_set, NullMatchingBehavior null_matching_behavior = NullMatchingBehavior::MATCH) Do you mean we remove the member variable `skip_nulls` and make it a parameter in constructor function and then translate the `skip_nulls` to `NullMatchingBehavior` ? I think this way will affect some users who set `skip_nulls` directly via member variable. Does it ok? If we don't remove member variable `skip_nulls, the translation problem still exists. For example: ``` SetLookupOptions option(value_set); option.skip_nulls = true; ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: github-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
