mirror of
https://github.com/scylladb/scylladb.git
synced 2026-05-28 10:41:12 +00:00
ad285c3c84
column_specification_or_tuple was introduced since some terms were prepared using a single receiver e.g. (receiver = <term>) and some using multiple receivers (e.g. (r1, r2) = <term>. Some term types supported both. To hide this complexity, the term->expr conversion used a single interface for both variations (column_expression_or_tuple), but now that we got rid of the term class and there are no virtual functions any more, we can just use two separate functions for the two variants. Internally we still use column_expression_or_tuple, it can be removed later.