[GitHub] [arrow-datafusion] alamb commented on issue #6223: RFC: move TypeConversion Checker into `cast_to()`

["alamb (via GitHub)" <gi...@apache.org>]

alamb commented on issue #6223:
URL: https://github.com/apache/arrow-datafusion/issues/6223#issuecomment-1534956778

   Splitting the "what is the result type of this expression" calculation from "what types should the inputs be coerced to to execute it" is a great idea in my opinion.
   
   I also think it would make the code much easier to reason about if the input arguments were coerced once (during type coercion in the analysis phase) and then never again. Right now I can never quite tell if the inputs to an expr have been coerced or not


-- 
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-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org