refactor(expr): decouple macro gen_binary_expr_atm from temporal operator signatures #1985
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.
What's changed and what's your intention?
The macro
gen_binary_expr_atm
currently list certain combinations of temporal types, e.g.timestamp_timestamp_f
,timestamp_interval_f
. This makes it harder to add more temporal operators as their signatures are not that regular compared to numbers. It makes less sense to reuse them acrossadd
/sub
/mul
/div
. For details, check the pg operator table below.This PR allows
gen_binary_expr_atm
to pass thru a list togen_atm_impl
directly, so that different operators (add
/sub
/mul
/div
) can add their own implementations without touching the definition ofgen_binary_expr_atm
any more.Query:
Checklist
- [ ] I have added necessary unit tests and integration tests(Refactor does not break existing tests.)Refer to a related PR or issue link (optional)