centralize the type coercion code for InList rule
Open
- Dominant language
- Rust
- Stars
- 9.3k
- Forks
- 2.4k
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 344
Description
Do we need a common function in a new file like `in_list_rule.rs` to do the `coerce_types`?
cc @alamb @andygrove
_Originally posted by @liukun4515 in https://github.com/apache/arrow-datafusion/pull/3472#discussion_r970347546_
Contributor guide
Research direction
Start by locating the existing `coerce_types` code used by the InList rule and review the discussion linked from the original post. Determine whether a shared function belongs in a new `in_list_rule.rs` file, then confirm that the InList rule uses the centralized implementation without changing its behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100